fix: ignore other prerelease tags when finding latest tag #213
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.
This relates to issue #211
If we have already git tags:
and then try to determine the next tag for prerelease
a
, we getv1.0.0-a.0
(which already exists).This is because
lib/latest-semver-tag.js
was returning the latest tag, even if it was different prerelease (b
in this case).This PR adds filtering to remove prerelease tags for different prereleases, and only then selecting latest