3 ms·
I find it interesting that nobody noticed this before public release. And apparently this version is a pre-release? But that isn't specified on the blog post?
by obw 9y ago
I find it interesting that nobody noticed this before public release. And apparently this version is a pre-release? But that isn't specified on the blog post?
- Piskvorrr 9y agoAnd even worse, 5.6.0 to 5.7.0 is, by semver, one minor point release to another minor point release - no breaking changes, no major bugs. 5.7.0-pre would raise some flags.
- floatboth 9y agoUhh. Does semver actually say anything about bugs?! o_0
- romanovcode 9y agoI'm pretty sure you don't release pre-release versions without -pre or -beta or -rc tags in the end.
- dan15 9y agoTechnically you don't have to with semver, it's just a good practice. From https://semver.org/ https://semver.org/: > A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Note that it says "MAY" and not "MUST", so it's optional.
- Piskvorrr 9y agoI'm pretty sure that "we're now changing permissions willy-nilly" is both a breaking change (which would warrant a major version bump, as per semver), and a bug (even though it's presented as an improvement by the authors). I should have been more clear.
- seba_dos1 9y agoWhat's more, while "npm install -g npm" correctly installs 5.6.0, "npm update -g npm" installs this apparently pre-release 5.7.0 version.