semantic versioning

A version numbering scheme of three numbers, major.minor.patch, raised for breaking changes, new features and fixes respectively.

In more detail

Increase the patch number for backwards-compatible bug fixes, the minor number for backwards-compatible new features and the major number for breaking changes, so 1.4.2 to 2.0.0 warns users that something will break. It is the publisher's promise rather than a guarantee, so updates still deserve review.

Examples

Ansible collections use semantic versioning, so ansible.posix 2.0.0 may break playbooks written for 1.x.
The lesson bumps [1, 2, 3] to 1.2.4 (patch), 1.3.0 (minor) and 2.0.0 (major).
Changesets picks the highest bump requested by the pending changes for each package.
dist/calc-2.4.0.tar
v1.3.0 is the canary and v1.2.0 the stable version traffic returns to.
Conventional Commits maps onto it: fix gives a patch bump, feat a minor bump and a breaking change a major bump.
git tag -a v1.0 -m 'Release version one'
1.2.0 → 1.3.0 new input added (compatible)
1.3.0 → 2.0.0 output renamed (breaking)
In Terraform: Providers and registry modules follow it, which is what makes the ~> operator safe. A module that renames or removes an input or output must release a new major version. The number is only a promise; the changelog and the plan are what you actually check.
In this course: Versioning a contract the same way tells consumers when they must change their code and when an update is safe. Minor versions add features compatibly, and patch versions only fix bugs.

Related terms

Taught in

References

Certification courses