Select the requested tag when publishing a stable release - #140
Merged
Conversation
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.
When a stable release and its last candidate point to the same commit, GoReleaser's default tag ordering can select the candidate even though the workflow verified the stable tag. The 1.0.0 publish attempt selected rc.24 and stopped when it reached the immutable candidate release.
Pass the workflow's resolved tag as
GORELEASER_CURRENT_TAGduring publication, using GoReleaser's documented override for multiple tags on one commit. This also lets the workflow safely retry the existing 1.0.0 tag without moving it or modifying the published candidate release.Validation: reproduced with the exact GoReleaser 2.18.0 binary in a disposable repository with annotated v1.0.0 and v1.0.0-rc.24 tags on the same commit. Without the override, metadata selected rc.24; with it, metadata and the built executable report 1.0.0.
git diff --checkpasses. No application or palette changes.Reference: https://goreleaser.com/resources/cookbooks/set-a-custom-git-tag/