mirror of
https://github.com/semver/semver.git
synced 2026-07-10 19:50:47 -05:00
[GH-ISSUE #26] Definitions of versions should include zeroes #5137
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vdtoorn on GitHub (May 25, 2012).
Original GitHub issue: https://github.com/semver/semver/issues/26
in item 7. 8. and 9:
Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.
Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API. It MAY include minor and patch level changes. Patch and minor version MUST be reset to 0 when major version is incremented.
the conditions x>0 look out of place, shouldn't that be x>=0, y>=0 and z>=0 at their respective descriptors?
@ayust commented on GitHub (Jun 7, 2012):
Seems more like those requirements are intended to only apply strictly after the first public API is released (1.0.0), and thus the conditions are correct.
@haacked commented on GitHub (Oct 2, 2012):
Exactly what @ayust said. Earlier in the spec it says:
The
x > 0is meant to make it clear that the rule about changing these version segments only applies when x is greater than 0.@arthurliraprof4-boop commented on GitHub (Jun 14, 2026):
https://github.com/semver/semver/issues/26