feat: prefixes for release tags #1079
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
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.
Adds support for applying prefixes to release tags. This way, you can have two branches with overlapping version numbers (I believe this only makes sense if you are publishing these branches as different packages).
If you change this on a project with an existing version history, you should manually tag your latest release with the new prefix so that the next time the version is bumped, it detects the latest version properly.
GitHub releases are now named after the release tag that is saved in dist/releasetag.txt after the
releasetask is run. By default, no prefixes are applied, so the releases will still just be named like "v1.2.3".By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.