[GH-ISSUE #447] Should lower places be reset to 0 when higher places are incremented? #1192

New Issue

GiteaMirror · 2026-04-16T10:30:30-05:00

GiteaMirror commented

2026-04-16 10:30:30 -05:00

Originally created by @jacktose on GitHub (Jun 6, 2018).
Original GitHub issue: https://github.com/semver/semver/issues/447

I assume that when you increment Major, Minor and Patch are reset to 0, and when you increment Minor, Patch is reset to 0.
e.g. 2.6.5 -> 2.7.0, 2.7.3 -> 3.0.0
not 2.6.5 -> 2.7.5, 2.6.5 -> 2.7.6, 2.6.5 -> 2.7.2, 2.7.3 -> 3.7.3, or anything like that.

However, that doesn't seem to appear in the spec. If that is supposed to be the case, I suggest adding it as a SHOULD or a MUST.

I don't know whether it should apply to pre-release versions or build metadata. Maybe as a SHOULD?

Originally created by @jacktose on GitHub (Jun 6, 2018). Original GitHub issue: https://github.com/semver/semver/issues/447 I assume that when you increment Major, Minor and Patch are reset to 0, and when you increment Minor, Patch is reset to 0. e.g. `2.6.5 -> 2.7.0`, `2.7.3 -> 3.0.0` not `2.6.5 -> 2.7.5`, `2.6.5 -> 2.7.6`, `2.6.5 -> 2.7.2`, `2.7.3 -> 3.7.3`, or anything like that. However, that doesn't seem to appear in the spec. If that is supposed to be the case, I suggest adding it as a SHOULD or a MUST. I don't know whether it should apply to pre-release versions or build metadata. Maybe as a SHOULD?

GiteaMirror closed this issue

2026-04-16 10:30:30 -05:00

GiteaMirror commented

2026-04-16 10:30:31 -05:00

@jacktose commented on GitHub (Jun 6, 2018):

Never mind, I missed this text:

... Patch version MUST be reset to 0 when minor version is incremented.

... Patch and minor version MUST be reset to 0 when major version is incremented.

@jacktose commented on GitHub (Jun 6, 2018): Never mind, I missed this text: > 7. ... Patch version MUST be reset to 0 when minor version is incremented. > 8. ... Patch and minor version MUST be reset to 0 when major version is incremented.

GiteaMirror referenced this issue

2026-04-16 10:58:51 -05:00

[GH-ISSUE #1192] sematics #1571

GiteaMirror referenced this issue

2026-04-20 10:26:09 -05:00

[GH-ISSUE #1192] sematics #2438

GiteaMirror referenced this issue

2026-04-25 17:44:25 -05:00

[GH-ISSUE #1192] sematics #3420

GiteaMirror referenced this issue

2026-06-13 13:20:56 -05:00

[GH-ISSUE #1192] sematics #4949