Release run #28 build succeeded, but the push failed with 401 Unauthorized: reqPackageAccess — Forgejo's injected GITHUB_TOKEN isn't scoped for container-registry writes.
Swaps secrets.GITHUB_TOKEN for secrets.REGISTRY_TOKEN (a PAT with write:package scope, added to repo secrets). Also removes the transient diagnostics step since we now know the failure mode.
Test plan
Post-merge: release.yml run succeeds end-to-end
git.fabledsword.com/bvandeusen/minstrel:main appears in the Forgejo package registry (closes Fable task 281, milestone M0)
Release run #28 build succeeded, but the push failed with `401 Unauthorized: reqPackageAccess` — Forgejo's injected `GITHUB_TOKEN` isn't scoped for container-registry writes.
Swaps `secrets.GITHUB_TOKEN` for `secrets.REGISTRY_TOKEN` (a PAT with `write:package` scope, added to repo secrets). Also removes the transient diagnostics step since we now know the failure mode.
## Test plan
- [ ] Post-merge: release.yml run succeeds end-to-end
- [ ] `git.fabledsword.com/bvandeusen/minstrel:main` appears in the Forgejo package registry (closes Fable task 281, milestone M0)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Release run #28 build succeeded, but the push failed with
401 Unauthorized: reqPackageAccess— Forgejo's injectedGITHUB_TOKENisn't scoped for container-registry writes.Swaps
secrets.GITHUB_TOKENforsecrets.REGISTRY_TOKEN(a PAT withwrite:packagescope, added to repo secrets). Also removes the transient diagnostics step since we now know the failure mode.Test plan
git.fabledsword.com/bvandeusen/minstrel:mainappears in the Forgejo package registry (closes Fable task 281, milestone M0)