fix: chain goreleaser into release-please workflow#16
Merged
Conversation
GITHUB_TOKEN-triggered tag pushes don't trigger other workflows, so the separate release.yml never ran. Chain the goreleaser job directly into release-please.yml so binaries get built on release. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This was referenced Mar 17, 2026
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
2 participants
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.
Summary
release.yml) triggers on tag pushes, but tags created by Release Please usingGITHUB_TOKENdon't trigger other workflows (GitHub Actions security limitation)release-please.ymlso it runs immediately after a release is createdTest plan
bin/install.shcan download the binary🤖 Generated with Claude Code