npm - Why do angular releated projects do not use semver 2.0 for prerelease tags? -
a lot of angular related projects use pre-release versioning scheme of following:
e.g. angular-cli
1.0.0-beta.22, 1.0.0-beta.22-1, 1.0.0-beta.24
e.g. @angular/material
2.0.0-alpha.9 2.0.0-alpha.9-1, 2.0.0-alpha.9-2, 2.0.0-alpha.9-3, 2.0.0-alpha.10, 2.0.0-alpha.2.0.0-alpha.11, 2.0.0-alpha.11-1,
due way semantic versioning works (dot separators, numeric lower precedence alphanumeric parts), 2.0.0-alpha.9-experimental-pizza still highest version @angular/material, tough 2.0.0-alpha.11 released.
similar angular-cli, 1.0.0-beta.22-1 still highest version, though 1.0.0-beta.24 released.
this causes package.json dependencies ^ versions, e.g.
"angular-cli" : "^1.0.0-beta.22-1"
to not upgrade 1.0.0-beta.24, because 24 numeric version , therefore smaller 22-1. posted issue @angular/material issue tracker here got no response.
is oversight, or missing something?
update:
angular-cli has versions
angular-cli@1.0.0-beta.25 angular-cli@1.0.0-beta.25.1 angular-cli@1.0.0-beta.25.2 angular-cli@1.0.0-beta.25.3 etc.
so seems oversight.
short answer these manual processes. team hasn't invested in automating them yet. @ least that's speaking angular cli, since i'm contributor repository source code (but not team member).
in pretty recent releases, happened @ release, had issue version. hence things 1.0.0-beta.xx
, has been followed 1.0.0-beta.xx-1
.
some tests hard run before publishing packages. cli publishes range of packages not 1 (a couple webpack plugins cli uses available separate packages other non-cli seed projects use).
usually when team happy version, explicitly tag
latest
, npm allows publishers do, so, shouldn't in theory have angular material alpha 9 vs alpha 11 problem, unless alpha 11 not tagged latest or something.
Comments
Post a Comment