2cd7283ce9841daabe7702449c3d5d61be683a48
Build and push server image / build-and-push (push) Successful in 41s
The automatic GITHUB_TOKEN doesn't reliably authenticate against Gitea's Container Registry -- confirmed as a known, still-open limitation across several Gitea versions (multiple upstream issues, consistent with the 401/unauthorized error hit here). Gitea's own community guidance is to use a real Personal Access Token instead. Switches docker/login-action to a REGISTRY_TOKEN repo secret (a PAT with package write scope, created in Gitea's user settings) with an explicit username rather than the gitea.actor context, and drops the now-unused permissions: packages: write block that only applied to the auto token.