mirrors/semver
0
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2025-08-28 00:35:30 +00:00
Code
Semantic Versioning Specification
159 Commits 3 Branches 4 Tags 670 KiB
Markdown 100%
74df6f3e4a
Go to file
Sly Gryphon 74df6f3e4a Change MUST reset to SHOULD reset 
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.
2025-07-22 08:45:21 +10:00
.github/workflows Update GHA workflow 2022-07-21 17:12:23 +09:00
.gitignore feat: Added linter and workflow; Fixed linter warnings 2020-06-18 16:50:54 +03:00
.remarkrc feat: Added linter and workflow; Fixed linter warnings 2020-06-18 16:50:54 +03:00
CODE_OF_CONDUCT.md Code of conduct: Use https links 2020-06-22 18:09:22 -07:00
CONTRIBUTING.md Refine the contributing guide 2023-05-07 10:05:23 +09:00
package-lock.json Run npm audit --force 2022-07-26 21:08:00 +09:00
package.json Run npm audit --force 2022-07-26 21:08:00 +09:00
README.md Refine the contributing guide 2023-05-07 10:05:23 +09:00
semver.md Change MUST reset to SHOULD reset 2025-07-22 08:45:21 +10:00
semver.svg Add railroad-diagram svg 2013-07-24 15:05:22 -07:00

README.md

Semantic Versioning Specification

"Semantic Versioning" or "SemVer" contains a set of rules and requirements that dictate how version numbers are assigned and incremented. You can find the full document in semver.md or visit our official website semver.org to find previous versions and localized specifications.

Changes to the document are published to the website by a GitHub Actions workflow which runs once each day.

Contributing

See the contribution guide.