the lastest version numbers have gone back in time
See original GitHub issuetechnically, the latest version (v2.0.0-alpha.7) is a lower version than v2.0.0 from March… in npm v3.10, this command installs v2.0.0:
$ npm i koa@^2.0.0-alpha
Only a mild annoyance, but "koa": "^2.0.0-alpha"
in my package.json doesn’t install the latest release as desired.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Restore an earlier version of a spreadsheet in Numbers on Mac
View, copy, and restore an earlier version With the spreadsheet open, choose File > Revert To (from the File menu at the top...
Read more >Version Numbering September 01, 2021 - Michael R Sweet
Version numbering has long been a source of pain in software. Early programs either lacked version numbers or used integers (“version 1”, “ ......
Read more >Understanding software version numbers: The complete guide
Does decoding software version numbers seem like a puzzle to you? Read our blog & find out the science behind software versioning.
Read more >Software versioning - Wikipedia
Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software.
Read more >The Amazing World of Version Numbers
Is there a funniest version number of all time? ... And Lotus SmartSuite Millennium Edition turned out to be the last real upgrade...
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
The issue is valid, and actually has nothing to do with
npm
, it’s down to this project’s release management; the release/tag management of the project in github.The project has a release
2.0.0
which is older than the latest2.0.0-alpha.X
releases.This availability of release
2.0.0
supersedes2.0.0-alpha.X
releases, this is basic semver. Therefore anyone trying to install using semver2.0.0-alpha.X
will get the outdated2.0.0
release and not the latest2.0.0-alpha.X
release.The project should remove release
2.0.0
as it is not2.0.0
due to2.0.0-alpha.X
tags still being released… see the release history.(replace release w/ tag etc)
Sidenotes;
@75lb using
^2.0.0-alpha
will install anything up to3.0.0
– basic semver… your app could break at any time 😉@jonathanong using
next
is a bit like usingmaster
, just slightly more controlled 😉@jonathanong remove the “2.0.0” release tag… 😉
Test yourself @ http://jubianchi.github.io/semver-check/
https://github.com/koajs/koa/issues/812