Semantic Version Bumper
Bump a version by major, minor, patch or pre-release and compare two versions using SemVer rules.
Optional v prefix; build metadata is dropped on bump.
Used by the pre-* bumps, for example rc, beta or alpha.
1.4.2 is older than 1.5.0.
How to use
Enter the current version, for example 1.4.2.
Copy the bumped version you need from the list.
Optionally enter a second version to see which one has higher precedence.
Example
Release candidate to release
Bumping a pre-release to its own release drops the suffix instead of jumping to 3.0.0.
2.0.0-rc.1 with a major bump
2.0.0
Frequently Asked Questions
No. SemVer ignores the part after + when deciding precedence, so 1.0.0+a and 1.0.0+b are equal.
Capabilities
- Major, minor, patch bumps
- Pre-major, pre-minor, pre-patch and pre-release
- Custom pre-release identifier
- Precedence comparison
- Strict SemVer validation
Related Tools
Compile semantic release notes grouped by Added, Changed, Deprecated, and Fixed.
Check a commit message against the Conventional Commits format and see exactly what to fix.
Craft clear, reviewer-friendly PR summaries with test plans and breaking change warnings.
Generate sleek Shields.io badges for tech stacks, social profiles, and open source repositories.
Explore
Connected career roadmaps, algorithmic problems, and real-world curricula related to Semantic Version Bumper.
Clear, milestone-driven paths from first fundamentals to your target engineering role.
Backend Engineer / Distributed Systems Developer · 8-12 months
Full-Stack Software Engineer · 8-12 months
DevOps / Cloud Infrastructure Engineer · 8-12 months
Cybersecurity Analyst / AppSec Engineer · 8-12 months