butterrobot/.github
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Felipe M. 279f4ba656
All checks were successful
CI / goreleaser-lint (push) Successful in 6s
CI / format (push) Successful in 2m47s
CI / lint (push) Successful in 3m50s
CI / test (push) Successful in 4m51s
CI / build (push) Successful in 3m48s
Release / release (push) Successful in 3m37s
ci: use ACTIONS_TOKEN for the release
Both the container registry login and goreleaser's GITEA_TOKEN now read
secrets.ACTIONS_TOKEN.

FORGEJO_TOKEN authenticated but was not authorised to write packages: the
docker login step succeeded while every blob upload returned

  401 Unauthorized  POST /v2/fmartingr/butterrobot/blobs/uploads/

which is what Forgejo returns when the bearer token minted at /v2/token
carries no push scope for the repository. That blocked the v0.12.0 release
after the binaries, archives and images had all built.

Claude-Session: https://claude.ai/code/session_01W7tcpMTEyk9RrHvT7Be5zZ
2026-09-21 17:07:40 +02:00
..
workflows ci: use ACTIONS_TOKEN for the release 2026-09-21 17:07:40 +02:00