Repository navigation
fix(release): pin GORELEASER_CURRENT_TAG to the triggering tag - #58
Merged
Merged
Conversation
When two tags point at the same commit (v0.0.1 tagged on the v0.0.1-beta.8 commit), GoReleaser auto-detected v0.0.1-beta.8 as the current tag and tried to re-upload assets to the existing beta.8 release, failing with 422 already_exists. Pin the tag from github.ref_name so the release always targets the tag that triggered the workflow. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
1 participant
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.
Why
The v0.0.1 release run (29241194810) failed:
v0.0.1was tagged on the same commit asv0.0.1-beta.8, and GoReleaser's tag auto-detection pickedv0.0.1-beta.8as the current tag. It then tried to upload assets to the existing beta.8 release and every upload failed with422 already_exists.What
Set
GORELEASER_CURRENT_TAG: ${{ github.ref_name }}in the release workflow so GoReleaser always releases the tag that triggered the run, regardless of how many tags point at the commit.🤖 Generated with Claude Code