[PR #393] Change MUST reset to SHOULD reset #6786

New Issue

GiteaMirror · 2026-06-17T05:35:46-05:00

GiteaMirror commented

2026-06-17 05:35:46 -05:00

📋 Pull Request Information

Original PR: https://github.com/semver/semver/pull/393
Author: @sgryphon
Created: 9/7/2017
Status: 🔄 Open

Base: master ← Head: feature/should-reset-instead-of-must

📝 Commits (1)

74df6f3 Change MUST reset to SHOULD reset

📊 Changes

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

View changed files

📝 semver.md (+8 -8)

📄 Description

As this is relaxing a constraint, it would be a minor update (2.1) to the specification - all existing implementations would remain compliant.

The relaxation of the increment by 1 requirements from SemVer 1.0 allowed, where it was necessary, to skip an increment, e.g. from release 2.4.10, change to 2.6.0 (or 4.0.0).

But, as the specification currently stands it would not be possible change from 2.4.10 to 2.5.1 - it MUST be 2.5.0 (or 2.6.0, etc).

Changing from MUST to SHOULD still encourages the reset, but allows for situations where it is not followed.

Example, moving from version 2.4.10, there could be an extensive period of 3.0.0-beta.1, 3.0.0-beta.2, etc, that never actually gets released, but is widely known; if the decision is made to skip a version, then this change would allow 3.1.0 to be developed (releasing 3.1.0-beta.1, etc) and eventually released (as 3.1.0). Without this change, the only option would be to bump to 4.0.0.

_{🔄 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/393 **Author:** [@sgryphon](https://github.com/sgryphon) **Created:** 9/7/2017 **Status:** 🔄 Open **Base:** `master` ← **Head:** `feature/should-reset-instead-of-must` --- ### 📝 Commits (1) - [`74df6f3`](https://github.com/semver/semver/commit/74df6f3e4a8014ea9ae5942ce23c02cebfc57e69) Change MUST reset to SHOULD reset ### 📊 Changes **1 file changed** (+8 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `semver.md` (+8 -8) </details> ### 📄 Description As this is relaxing a constraint, it would be a minor update (2.1) to the specification - all existing implementations would remain compliant. The relaxation of the increment by 1 requirements from SemVer 1.0 allowed, where it was necessary, to skip an increment, e.g. from release 2.4.10, change to 2.6.0 (or 4.0.0). But, as the specification currently stands it would not be possible change from 2.4.10 to 2.5.1 - it MUST be 2.5.0 (or 2.6.0, etc). Changing from MUST to SHOULD still encourages the reset, but allows for situations where it is not followed. Example, moving from version 2.4.10, there could be an extensive period of 3.0.0-beta.1, 3.0.0-beta.2, etc, that never actually gets released, but is widely known; if the decision is made to skip a version, then this change would allow 3.1.0 to be developed (releasing 3.1.0-beta.1, etc) and eventually released (as 3.1.0). Without this change, the only option would be to bump to 4.0.0. --- <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-06-17 05:35:46 -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#6786