🐛 Fixes wrong order of pre-release tags #274
Open
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
evilru
force-pushed
the
fix/order-of-pre-release-tags
branch
from
254d36e
to
d5161b4
Compare
replace npm package semver-compare with compare-versions it has support for pre-release tags
This verifies that the recent change from npm package semver-compare to compare-versions solves wrong order of pre-release tags
evilru
force-pushed
the
fix/order-of-pre-release-tags
branch
from
d5161b4
to
93eb682
Compare
evilru
force-pushed
the
fix/order-of-pre-release-tags
branch
from
93eb682
to
cb0965a
Compare
evilru
changed the title
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.
Replaced the package semver-compare with compare-versions.
semver-compare dosn't have support for pre-release tags and does not sort it properly
where compare-versions does.
Added an e2e test covering the issue I run into during init.