-
Notifications
You must be signed in to change notification settings - Fork 25
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
Intended behavior for 1.*.1 #62
Comments
It should fail to parse, yes. If there are existing packages with versions on crates.io that are incorrect, we could add them into https://github.com/steveklabnik/semver/blob/051c39c50d565c597be65c4496597c7d16a514d9/src/version_req.rs#L323-L332 to keep compatibility, but the intention isn't for this sort of version to parse properly. semver/semver#584 is the spec I intend to follow once I get around to actually finally double checking everything and getting it in. |
This is fixed in 1.0.0. fn main() {
println!("{}", semver::VersionReq::parse("1.*.1").unwrap_err());
} unexpected character after wildcard in version req |
My expectation is that
1.*.1
is not a meaningful version req and should fail to parse. However I don't have a spec to point to so I just wanted to confirm whether semver-parser's current behavior on this case is intended.As of the most recent release (0.10.2) semver-parser parses it as follows, i.e.
>=1.0.0, <2.0.0
.The text was updated successfully, but these errors were encountered: