-
-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm setPackageVersion semver2 support #236
Milestone
Comments
Does NPM support semver2 consistently everywhere, or should it be an option for folks to use semver1 or 2? And which should be the default. |
I'm finding semver2 usage as far back as six years ago here (history page). So it sure seems like semver2 should be the default (and in fact only) option. |
AArnott
added a commit
that referenced
this issue
Nov 25, 2018
This has been around and supported for at least six years in NPM. Fixes #236
AArnott
added a commit
that referenced
this issue
Nov 25, 2018
This has been around and supported for at least six years in NPM. Fixes #236
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
setPackageVersion is a nice helper function to update the version in a package.json file. Today it looks like it will always spit out a semver1 version. It would be nice if it could be parameterized to support semver2, as npm as semver2 support.
The text was updated successfully, but these errors were encountered: