semver fails when it comes to pre-releases
See original GitHub issueSteps to reproduce
- Change the version in
package.json
from1.7.44
to something like1.7.44-build1
npm run metadata:generate
npm run test
Google’s demo link
N/A
See also: https://github.com/substack/semver-compare/issues/1 .
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Resetting of pre-release and build versions... #60 - GitHub
Suppose SemVer did state you must reset the pre-release version when incrementing a version. How could that make sense? Suppose you release 1.0....
Read more >Node app fails to run because of prerelease - Stack Overflow
The change in handling prerelease versions in semver@4 is one of the primary motivators for the major version bump to npm@2.
Read more >semver - npm Docs
Identifier to be used to prefix premajor, preminor,. prepatch or prerelease version increments. -l --loose. Interpret versions and ranges ...
Read more >Prerelease in semver - Rust - Docs.rs
The SemVer spec's rule for pre-release precedence has special treatment of numeric components in the pre-release string, but only if there are no...
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format. Introduction. In the world of software ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Published
libphonenumber-js@1.7.46
. https://github.com/substack/semver-compare/issues/1#issuecomment-594765531Actually, I could do this quick fix myself. Maybe in the evening.
On Wed, 4 Mar 2020 at 03:22, Alan Liang notifications@github.com wrote: