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.
In the background I've been chipping away at what support for "pre-release versions" would look like in
bump
.In short, the non-edge case version of this would be something like:
1.2.3-rc.2
should suggest1.2.3-rc.3
and1.2.3
as the next two possibilities). Since there is no required format for prerelease field contents in semver, need to detect, parse, and increment all of the most common format possibilities (e.g.-rc.1
,-rc1
,-1
, etc etc etc.) while preserving the user's original schematic.rc.1
or some such. Whether these less common options are always visible (whatnp
does, easy but kinda ugly/confusing to always have it there), or are special cased with--pre
CLI flag or something, is an open UX question.Some bulleted requirements:
getLatest
on releases ignores prerelease flagged releases! Need to iterate entire list ourselves and build out own results.