build: allow release workflow to be manually triggered against a tag#4283
Merged
Conversation
Add a 'tag' input to the workflow_dispatch trigger so releases can be re-run or initiated manually for a specific tag. The checkout step uses the provided tag, and GORELEASER_CURRENT_TAG is set so goreleaser picks up the correct version. A validation step ensures non-dry-run releases require a tag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
aarzilli
approved these changes
Mar 10, 2026
|
Is it possible to use this now to publish artifacts for the previous release? |
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
3 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.
Add a 'tag' input to the workflow_dispatch trigger so releases can be re-run or initiated manually for a specific tag. The checkout step uses the provided tag, and GORELEASER_CURRENT_TAG is set so goreleaser picks up the correct version. A validation step ensures non-dry-run releases require a tag.