Semantic Version Bumper
Bump a semver string by major, minor, patch or prerelease.
How to use
- 1 Enter your current version (a leading "v" is allowed).
- 2 Pick the release type: major, minor, patch or a prerelease variant.
- 3 For prerelease types, set the identifier such as beta or rc.
- 4 Copy the computed next version.
About Semantic Version Bumper
The Semantic Version Bumper takes a SemVer string such as 1.4.2 and computes the next version for a given kind of release, following the rules of the Semantic Versioning specification.
Choose major to signal breaking changes, minor for backward-compatible features, or patch for bug fixes; the tool resets the lower components correctly, so a minor bump on 1.4.2 becomes 1.5.0 and a major bump becomes 2.0.0.
It also understands prereleases.
The premajor, preminor and prepatch options jump to the next stable target and attach a prerelease tag like 2.0.0-beta.0, while the prerelease option increments an existing numeric tag (beta.1 → beta.2) or starts one on a stable version.
You can customise the prerelease identifier — beta, alpha, rc or anything you like.
A plain patch bump applied to a prerelease simply finalises it by dropping the tag, which matches how most release tooling behaves.
Input may include a leading v and optional build metadata; build metadata is dropped on a bump as the spec recommends.
Everything runs locally, updates instantly, and never leaves your browser, so it is a quick sanity check before you tag a release.
FAQ
What happens to build metadata when I bump?
It is dropped, as the SemVer spec treats build metadata as ignorable and not carried across version increments.
How does a patch bump treat a prerelease version?
A patch bump on 1.2.3-beta.1 finalises it to 1.2.3 by removing the prerelease tag, matching common release tooling.