Glossary Updates12 new terms added to the glossaries · October 2, 2026, 22:44 CEST
AI TechDocKnowledge

Glossary · Automation software engineering and architecture

Patch version

Also known as: Patch level, Bugfix version

German: Patch-Version

In software versioning, the patch version is the third number of a version identifier such as 3.1.4; under semantic versioning it is incremented for backward-compatible bug fixes only.

  • Software engineering

In one sentence

The patch version is the third number of a version identifier; semantic versioning raises it for backward-compatible bug fixes only.

Example

Firmware 4.2.1 fixes a wrong unit in a diagnostic message of version 4.2.0 without adding features, so it is released as a patch version.

How it applies

  • Engineering: A patch release contains fixes only. Mixing new features into it breaks the expectations of users who install patches with little testing.
  • Maintenance: Operators apply patch versions more readily than minor or major ones; Patch management processes still require checking the fix list against the plant's use.
  • Documentation: Every patch needs a Release note listing the fixed defects in user terms. The manual itself rarely changes, but corrected behavior that the manual described wrongly must be updated.

Patch version vs. security patch

The patch version is a numbering convention. A security patch is a fix for a vulnerability, which may be released as a patch version, but also as a hotfix outside the regular numbering.

By knowledge.aitechdoc.world · Published September 26, 2026 · Last reviewed

Source: Semantic Versioning 2.0.0 (semver.org)

Definitions follow the cited standards and specifications. Where a source is a copyrighted publication, such as an ISO, IEC or EN standard, the definition is a close paraphrase, not a verbatim quotation, so as not to infringe copyright. We recommend reading the original publication. The sections “How it applies” are editorial commentary by AI TechDoc Blog and are not part of any standard.

Seen a mistake? Send us a note!