Okuzeka
Software Engineering vocabulary · Release and Maintenance

Semantic versioning

Meaning in software engineering, with examples

nounAdvanced term

In software engineering, semantic versioning means: A version-numbering rule with three parts, MAJOR.MINOR.PATCH: the first number changes for breaking changes, the second for new features and the third for bug fixes.

In Turkish: semantik sürümleme, anlamsal sürümleme

How it is used

Often shortened to SemVer. For example, going from 2.3.1 to 3.0.0 tells users to expect breaking changes, while 2.3.2 should be a safe update. Package managers use these rules for version ranges such as ^2.3.0.

Example sentences

  1. We follow semantic versioning, so removing that endpoint means we have to release 4.0.0.

  2. Not every library follows semantic versioning strictly, so read the changelog before upgrading.

Common collocations

  • follow semantic versioning
  • SemVer
  • major version
  • minor version
  • patch version
  • releaseA version of a product that is made available to users, or the act of making it available. Also a verb: to release a new version.
  • breaking changeA change to an API, library or file format that makes existing code that uses it stop working unless that code is updated too.
  • patchA small update that fixes bugs or security problems in software without adding big new features. It is also a verb: to patch a system.
  • changelogA file or page that lists the notable changes in each version of a project, usually with the newest version first. It is often named CHANGELOG.md.

More terms: Release and Maintenance

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: