Patch
A patch is the final number in a version string such as 2.4.1.
In SemVer, a patch version is usually increased for backward-compatible bug fixes and small corrections.
What it does
A patch signals a low-scope release relative to minor or major changes.
It is commonly used to:
- Fix bugs
- Correct regressions
- Ship small safe improvements
- Release targeted maintenance updates
- Distribute urgent low-scope fixes such as a hotfix
Core concepts
Final position
In a version like 3.7.5, the 5 is the patch version.
Compatibility expectation
Under SemVer, a patch release should be backward compatible and should not introduce a breaking change.
Maintenance release
Patch releases are commonly associated with maintenance, stabilization, and issue correction rather than feature expansion.
Common use cases
- Bug fixes
- Small performance or stability improvements
- Post-release corrections
- Regression fixes
- Limited-scope maintenance updates
Practical notes
- A patch release is usually lower risk than a minor version or major version release, but not risk-free.
- A hotfix may be released as a patch version when the fix is small and backward compatible.
- Some teams misuse patch versions for larger changes, so judgment still matters.
- Good patch releases stay narrow in scope and easy to validate with QA.
Frequently Asked Questions
What is the patch version in 4.2.9?
It is 9.
Does a patch release mean only bug fixes?
Under strict SemVer, it usually means backward-compatible fixes and small corrections.
Can a hotfix be a patch release?
Yes. A hotfix is often distributed as a patch release when it is urgent but narrowly scoped.