Semantic Versioning
Definition
Semantic versioning indicates in version numbers what type of software change is present.
A versioning convention `MAJOR.MINOR.PATCH` that distinguishes incompatible changes, compatible features, and bug fixes.
Simply explained
The three numbers of a version indicate whether something fundamental, a feature, or only a bug has changed.
Why it matters in practice
The term contributes to secure, maintainable, and high-performance web applications as well as resilient technical decisions.
Example from business
An incompatible API change increases the major version from 2 to 3.
Limits and pitfalls
- Using SemVer without a defined public API or viewing version numbers as a quality guarantee.
Origin & history
Semantic Versioning was formalized from software packaging practice and disseminated as a public specification.
Use in mid-sized companies
- Possible example: An incompatible API change increases the major version from 2 to 3.
Frequently asked questions
What does Semantic Versioning mean?
A versioning convention `MAJOR.MINOR.PATCH` that distinguishes incompatible changes, compatible features, and bug fixes. What mistakes should be avoided? Using SemVer without a defined public API or viewing version numbers as a quality guarantee.
Sources
Source checked on 10.10.2026. Editorial application examples are hypothetical; no evidence of real customer results.
Editorially reviewed on: