Skip to content
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

Semver rule 4 specifies that 0.x.z, anything may change at anytime #4145

Closed

Conversation

nishtala
Copy link

@nishtala nishtala commented Dec 7, 2024

Semver rule #4 (https://semver.org/#spec-item-4) specifies that "
Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
"
The text currently says you can get the latest patch release that will still compile, which is incorrect for x.y.z | (x==0)

@chriskrycho
Copy link
Contributor

chriskrycho commented Dec 9, 2024

Rust has a slightly stricter interpretation than SemVer does—specifically, the Cargo resolver handles Default Requirements like this:

Default requirements specify a minimum version with the ability to update to [SemVer] compatible versions.
Versions are considered compatible if their left-most non-zero major/minor/patch component is the same.
This is different from [SemVer] which considers all pre-1.0.0 packages to be incompatible.

@chriskrycho chriskrycho closed this Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants