ci: give GoReleaser the GitHub token through its token file #87

Merged

jwarykowski merged 1 commit from ci/release-token into master

2026-10-25 12:33:13 +00:00

jwarykowski commented

2026-10-25 12:29:52 +00:00

Owner

On Forgejo Actions the runner's own GITHUB_TOKEN (Forgejo's) wins over the one a step sets, so GoReleaser would send a Forgejo token to GitHub and fail with 401 Bad credentials, as drover v0.3.0 just did. Same fix as keybars: check GH_RELEASE_TOKEN with gh api user, write it to GoReleaser's token file and unset GITHUB_TOKEN before releasing.

Merge before #85, which triggers the 0.21.0 release.

On Forgejo Actions the runner's own GITHUB_TOKEN (Forgejo's) wins over the one a step sets, so GoReleaser would send a Forgejo token to GitHub and fail with `401 Bad credentials`, as drover v0.3.0 just did. Same fix as keybars: check GH_RELEASE_TOKEN with `gh api user`, write it to GoReleaser's token file and unset GITHUB_TOKEN before releasing. Merge before #85, which triggers the 0.21.0 release.

jwarykowski added 1 commit

2026-10-25 12:29:52 +00:00

ci: give GoReleaser the GitHub token through its token file

pull-request / lint-and-test (pull_request) Successful in 1m15s

Details

7bc778b54b

jwarykowski merged commit c8e1c2b6e5 into master

2026-10-25 12:33:13 +00:00

jwarykowski deleted branch ci/release-token

2026-10-25 12:33:13 +00:00

jwarykowski referenced this pull request from a commit

2026-10-25 12:33:14 +00:00