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
Support for "~" version constraint operator for projects that use Semantic Versioning. #968
Conversation
Cool, fixes #643 partially too. If you'd like to work on the rest of those issues it'd be great :) |
btw, the behavior described in this PR for |
@stof Are you referring to the fact that the normalised versions as used in the unit tests refer to ">1.1.999999.999999" instead of ">=1.2.0"? I did this for consistency with the existing wildcard operators, though now I fear I may have misunderstood the intent there. |
@jmalloc no, I'm talking about the upper bound |
Guys, I'll close this and re-open once all the features in #643 are complete. |
As you wish, but if you don't have time to complete it please just reopen a PR with incomplete stuff, it's still better than nothing. |
Oh, I'm definitely working on it - I have a few of the features complete, I just thought it was getting a bit noisy. |
@jmalloc any news? :) |
This PR provides support for a new version constraint operator specified with the tilde character.
It behaves similarly to the operator of the same name in npm.
For example, specifying the version constraint as
~1.2.0
is functionally equivalent to>=1.2.0,<2.0.0
. If the package adheres to the semantic versioning specification then any version in this range is guaranteed to be compatible.