fix: add release version tag back to name format for assets #198
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
srinandan
approved these changes
May 4, 2023
Collaborator
|
Sai, perhaps we can delete v.1.120 and re-publish the tag after merging these changes? |
Collaborator
|
Sure - I can delete the tag/release and push it again v1.120 |
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.
Release version was removed from Asset name after updating
.goreleaser.yml.Adding this back to maintain a consistent naming convention for release artifacts.
Revert changes to
downloadLatest.shas these are no longer required if the version remains in the asset filename.Discussed in #195