Semver Version Bumper

How to use

1. 1Type your current version, for example 1.4.2, or click a sample like 2.0.0-rc.1. A leading v is accepted and ignored.
2. 2Read the seven next versions: major, minor, patch, and the four prerelease bumps, each with a one-line note on when to use it.
3. 3If you cut prereleases, set the prerelease id (rc, beta, alpha) and whether new tags start at 0 or 1 to match your project.
4. 4Add optional build metadata to append an identifier after a plus, such as build.42. It is parsed and shown but never affects ordering.
5. 5Copy a single version with its Copy button, or use Copy all to grab the full list. Everything runs in your browser.

About this tool

Semver Version Bumper answers a question that comes up on every release: given the version you are on now, what is the next version number for the change you just made. It complements a version comparator, which tells you whether one version is greater than another, by going the other way and computing the next number for you. Paste a Semantic Versioning 2.0.0 string such as 1.4.2, 0.9.0, or 2.0.0-rc.1, with or without a leading v, and the tool parses it into its major, minor, patch, prerelease, and build parts and shows seven standard bumps at once so you can copy the one you need. The three core bumps follow the SemVer specification exactly. A major bump is for incompatible API changes and resets minor and patch to zero, so 1.4.2 becomes 2.0.0. A minor bump is for backward-compatible new features and resets patch to zero, so 1.4.2 becomes 1.5.0. A patch bump is for backward-compatible bug fixes, so 1.4.2 becomes 1.4.3. All three drop any prerelease and build metadata, because a finished release supersedes a prerelease of the same core. The four prerelease bumps cover the cases people reach for when shipping release candidates and betas. Pre-major, pre-minor, and pre-patch start a fresh prerelease on the next breaking, feature, or fix version, while a plain prerelease bump advances an existing tag by incrementing its last number, or opens a new one on the next patch when there is no tag yet. You control the prerelease label (rc, beta, alpha, or anything valid) and whether a new tag starts numbering at zero or one, matching the convention your project already uses. The tool also mirrors the subtle rules the reference semver implementation uses: bumping the patch of a prerelease releases its core rather than incrementing, so 1.2.3-rc.1 patched becomes 1.2.3, and major or minor bumps of a prerelease whose lower parts are already zero release the core instead of moving past it. An optional build metadata field lets you append an identifier after a plus, like 1.0.0+build.42, which tools ignore when ordering versions. Every result updates live as you type, a short guide explains which bump to choose, and you can copy a single version or the whole list. Everything runs in your browser, so the version strings you type are never uploaded, and there is no signup and no account.

Free to use. Works in your browser. No signup, no login.