fix: Properly sort pre-release tags #63
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
Enable proper sorting or pre-release versions, after corresponding release version, as per https://github.com/git/git/blob/master/Documentation/config/versionsort.txt: By specifying a single suffix in this variable, any tagname containing that suffix will appear before the corresponding main release. This effectively implements proper semantic version ordering.
|
@caarlos0 Any chance we could get this in? |
|
amazing, thanks @jimmidyson ! |
|
@caarlos0 Thank you! |
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.
Enable proper sorting of pre-release versions, after corresponding
release version, as per https://github.com/git/git/blob/master/Documentation/config/versionsort.txt:
This effectively implements proper semantic version ordering.