Minor Version
A minor version is the middle number in a version string such as 2.4.1.
In SemVer, the minor version is usually increased for backward-compatible feature additions or meaningful improvements that do not introduce a breaking change.
What it does
The minor version signals meaningful but compatible change.
It is commonly used to:
- Mark new features
- Indicate product or API growth
- Separate feature releases from small bug-fix releases
- Communicate that older consumers should still work without forced changes
Core concepts
Middle position
In a version like 3.7.5, the 7 is the minor version.
Backward-compatible change
Under SemVer, a minor-version bump should not break existing users.
Feature release signal
Minor versions often represent a more meaningful step than a patch release while staying lower-risk than a major version.
Common use cases
- New features
- Compatible enhancements
- Expanded options or settings
- Non-breaking improvements to plugins, apps, or libraries
- Feature releases between major milestones
Practical notes
- Minor versions can still carry operational risk even when they are not supposed to be breaking.
- Teams often review minor-version releases more carefully than patch releases but less cautiously than major upgrades.
- In ecosystems that do not follow SemVer strictly, a minor version is only a hint, not a guarantee.
- Good release notes help users understand what a minor-version release actually adds.
Frequently Asked Questions
What is the minor version in 4.2.9?
It is 2.
Does a minor version mean no breaking changes?
Under strict SemVer, yes. In real projects, teams should still verify.
Why use a minor version bump?
Because it signals meaningful but backward-compatible progress.