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.
Motivation
The canary version names are not so good because they are not ordered properly.
If a user add a canary version name in package.json with a semver range like ^ he may end up with another older canary version where the commit hash starts with z.
Can be seen using https://semver.npmjs.com/
Once we add a letter to the party, it starts using alphabetical ordering:
Ie if I try to add the latest canary in package.json:
I finally end-up with another older canary
This is annoying behavior and requires advising users to not use semver ranges (when manual editing package.json or using --save-exact option)
Having a version name scheme that is self-increasing fixes the issue