Repository navigation
fix(ci): goreleaser reads GITHUB_TOKEN, not GH_TOKEN - #6
Merged
Merged
Conversation
The dispatch ran and failed in 19s with 'missing GITHUB_TOKEN, GITLAB_TOKEN and GITEA_TOKEN': goreleaser wants GITHUB_TOKEN, while gh wants GH_TOKEN. The release for v0.17.0 was created and is assets-less until this is re-run.
calionauta
force-pushed
the
fix/release-token
branch
from
October 25, 2026 18:39
281d734 to
4559235
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v0.17.0 release dispatch ran and failed in 19s: goreleaser wants
GITHUB_TOKENwhileghwantsGH_TOKEN, and the workflow only set the latter. The release exists and is assets-less until re-run.Verified by dispatching
release.ymlfor v0.17.0 after merge.