publish releases on the v prefix'd tag #4873
Merged
Conversation
This file contains 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
Skarlso
approved these changes
Mar 2, 2022
|
modified |
This reverts commit 0d08153.
aclevername
changed the title
Skarlso
approved these changes
Mar 3, 2022
nikimanoledaki
approved these changes
Mar 3, 2022
This was referenced Mar 4, 2022
Closed
7 tasks
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.
Description
Closes #4858
its super unclear how
goreleaserdecides what version to use for the release. This workflows trigger on thex.x.xtags (without thevprefix). You can use an environment variable to configure thisGORELEASER_CURRENT_TAGhttps://goreleaser.com/customization/build/?h=goreleaser_current_tag#define-build-tag. I'm setting with env var with thevprefix to change the version