[PR #251] [CLOSED] Changed MUST to MAY for resetting Minor and Patch when incrementing Majo... #3494

New Issue

GiteaMirror · 2026-04-25T17:46:02-05:00

GiteaMirror commented

2026-04-25 17:46:02 -05:00

📋 Pull Request Information

Original PR: https://github.com/semver/semver/pull/251
Author: @deanrather
Created: 4/24/2015
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (1)

34df496 Changed MUST to MAY for resetting Minor and Patch when incrementing Major

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 semver.md (+1 -1)

📄 Description

There is no need to reset the Minor version number when incrementing the Major, as the new Major version may include the same functionality as the previous Major version.

Patch version numbers need only be reset when the functionality changes. I.e. when the Minor Version is incremented.

Resetting the Minor version to Zero looses the Minor Version Number's helpfulness in seeing at-a-glance how many new feature versions have been developed.

This makes the following legal:

1.2.3 -> 2.2.3     // A compatibility-breaking change was introduced, but no patches or new functionality
1.2.3 -> 2.2.4     // A compatibility-breaking patch was introduced, but no new functionality
1.2.3 -> 2.3.0     // A compatibility-breaking feature was introduced
1.2.3 -> 2.0.0     // Any of the above combinations, but you can still reset both if you like!

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/semver/semver/pull/251 **Author:** [@deanrather](https://github.com/deanrather) **Created:** 4/24/2015 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`34df496`](https://github.com/semver/semver/commit/34df49653f517c3653738a95c365e88dd6c5bdb0) Changed MUST to MAY for resetting Minor and Patch when incrementing Major ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `semver.md` (+1 -1) </details> ### 📄 Description There is no need to reset the Minor version number when incrementing the Major, as the new Major version may include the same functionality as the previous Major version. Patch version numbers need only be reset when the functionality changes. I.e. when the Minor Version is incremented. Resetting the Minor version to Zero looses the Minor Version Number's helpfulness in seeing at-a-glance how many new feature versions have been developed. This makes the following legal: ``` 1.2.3 -> 2.2.3 // A compatibility-breaking change was introduced, but no patches or new functionality 1.2.3 -> 2.2.4 // A compatibility-breaking patch was introduced, but no new functionality 1.2.3 -> 2.3.0 // A compatibility-breaking feature was introduced 1.2.3 -> 2.0.0 // Any of the above combinations, but you can still reset both if you like! ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-25 17:46:02 -05:00

GiteaMirror closed this issue

2026-04-25 17:46:03 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#3494