-
Notifications
You must be signed in to change notification settings - Fork 472
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
[BUG] limit version prefix to optional v
#691
Comments
Added this to #501 |
I have done some analysis of all versions, dependencies and engine ranges used in the top 5200 npm
The use of
|
why even bother removing the |
Agree. Removing |
Is there an existing issue for this?
Current Behavior
The following "ranges" are currently considered valid: > v=1.2.3, > vvv1.2.3, > v==1.2.3, > v=vv==v1.x
The validation is not strict enough and allows
=
,v=
, and nonsensical prefixes as well.Expected Behavior
With next major semver, the version prefix should be limited to a single, optional
v
. Other prefixes shall not be permitted anymore.Suggested change:
Steps To Reproduce
Environment
The text was updated successfully, but these errors were encountered: