What is semantic versioning (SemVer)?

SemVer uses MAJOR.MINOR.PATCH — breaking changes bump major, features minor, fixes patch.

Semantic Versioning 2.0.0 signals API stability: 1.0.0 → 2.0.0 means breaking changes; 1.1.0 adds backward-compatible features. Pre-release tags (1.0.0-beta.1) sort before release.

npm, Cargo and most package registries assume SemVer ranges (^1.2.3). Tentaco automation docs link gitignore and release hygiene for maintainers shipping tools.