Semantic Versioning (SemVer)
A widely adopted software version numbering specification using the format MAJOR.MINOR.PATCH. Changes to each component communicate compatibility information, helping downstream dependents assess the risk associated with upgrading to a new version.
Core Facts
According to the Semantic Versioning (SemVer) specification, 0.y.z is in the initial development phase, any version may introduce breaking changes, and the public API should not be considered stable.
The Semantic Versioning (SemVer) format is MAJOR.MINOR.PATCH: a change in the major version number indicates backward-incompatible API changes, a change in the minor version number indicates new features that maintain backward compatibility, and a change in the patch number includes only bug fixes.
In the npm ecosystem, a range declaration such as ^3.0.25 automatically accepts patch and minor version upgrades, and running npm update will automatically fetch 3.0.26
Timeline (last 90 days)
After 1.0, minor versions are guaranteed to be backward compatible.
In semantic versioning, a minor version indicates backward-compatible feature additions.
According to the Semantic Versioning (SemVer) specification, 0.y.z is in the initial development phase, any version may introduce breaking changes, and the public API should not be considered stable.
In the npm ecosystem, a range declaration such as ^3.0.25 automatically accepts patch and minor version upgrades, and running npm update will automatically fetch 3.0.26
For PATCH-level versions, developers can theoretically upgrade directly without modifying any business code.
The Semantic Versioning (SemVer) format is MAJOR.MINOR.PATCH: a change in the major version number indicates backward-incompatible API changes, a change in the minor version number indicates new features that maintain backward compatibility, and a change in the patch number includes only bug fixes.
All Facts (6)
According to the Semantic Versioning (SemVer) specification, 0.y.z is in the initial development phase, any version may introduce breaking changes, and the public API should not be considered stable.
90%VerifiedThe Semantic Versioning (SemVer) format is MAJOR.MINOR.PATCH: a change in the major version number indicates backward-incompatible API changes, a change in the minor version number indicates new features that maintain backward compatibility, and a change in the patch number includes only bug fixes.
90%VerifiedIn the npm ecosystem, a range declaration such as ^3.0.25 automatically accepts patch and minor version upgrades, and running npm update will automatically fetch 3.0.26
80%UnverifiedIn semantic versioning, a minor version indicates backward-compatible feature additions.
70%UnverifiedAfter 1.0, minor versions are guaranteed to be backward compatible.
50%UnverifiedFor PATCH-level versions, developers can theoretically upgrade directly without modifying any business code.
50%