[BUG] ghcr.io/tinyauthapp/tinyauth:v5 image repo doesn't exist, org name not fully migrated for builds?

[pwntr]

Describe the bug

❯ docker pull ghcr.io/tinyauthapp/tinyauth:v5
Error response from daemon: manifest unknown

To Reproduce
try to pull the image and tag given in the docker compose example file

Expected behavior
Being able to pull the image under the new org name

Screenshots
n/a

Logs
see above

Device (please complete the following information):

• OS: Linux, Fedora 44, kernel 7.04
• Docker version 29.4.3, build 055a478

[dosubot]

Hi @pwntr! I'm Dosu and I’m helping the tinyauth team.

This looks like a real issue caused by the timing of the organization migration. Here's what's happening:

The project migrated from ghcr.io/steveiliop56/tinyauth to ghcr.io/tinyauthapp/tinyauth on April 26, 2026 [1]. However, the last versioned release (v5.0.7) was published on April 16, 2026 — before the migration. Since then, only a nightly tag has been pushed under the new org .

The release workflow does generate a v5 major version tag via the metadata-action config [2], but because no release has been cut since the migration, no versioned images (including the v5 tag) exist at ghcr.io/tinyauthapp/tinyauth.

Workarounds in the meantime:

• Pull from the old org: ghcr.io/steveiliop56/tinyauth:v5
• Or use the nightly build: ghcr.io/tinyauthapp/tinyauth:nightly

The fix would be to cut a new release (e.g., v5.0.8) under the new org, which would automatically create the v5, v5.0, and full semver tags at the new registry path.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[steveiliop56]

@pwntr we have migrated everything to the organization but we haven't released anything new for a new image to exist. The note in v5.0.7 says that every version after v5.0.7 will be released under the new organization name. So the moment you see a new version, the new image will be located only in this organization.

[pwntr]

Great, thanks for the info, noted! But then this example would probably need a note or an adjustment for the time being? Or could you manually push one release to the new org (same as current 5.0.7) so that examples and org migration are aligned right away? Would save some extra steps on both ends 😃.

[steveiliop56]

I will see if I can push the image to the new package. As for the example, you are looking at the main branch which is the development one and thus has the latest changes:

This is the main development branch. For the latest stable release, see the documentation or the latest stable tag.

[pwntr]

I will see if I can push the image to the new package. As for the example, you are looking at the main branch which is the development one and thus has the latest changes:

This is the main development branch. For the latest stable release, see the documentation or the latest stable tag.

My bad, thanks for the hint and also tinyauth itself 🤝!

[steveiliop56]

@pwntr we copied the v5, v5.0, v5.0.7 and latest tags to the new image. You should be able to pull them and use them normally.

[steveiliop56]

Also added the -distroless tags (v5-distroless, v5.0-distroless, v5.0.7-distroless).

[pwntr]

Awesome, can confirm both (with -distroless) pulling in my build now. Thanks so much 🙏 !