Skip to main content

Semantic Version Bumper

Enter a semver version and click a bump type to get the next version. Preview all bump results at a glance, configure pre-release and build metadata tags, and copy the new version instantly.

✓ Major / minor / patch / pre-release ✓ Live preview of all bump types ✓ Bump history with copy ✓ 100% browser — no server

Frequently Asked Questions

What is semantic versioning (semver)?▼

Semantic Versioning (semver) is a versioning scheme in the format MAJOR.MINOR.PATCH. MAJOR is incremented for breaking (incompatible) API changes. MINOR is incremented for new backward-compatible features. PATCH is incremented for backward-compatible bug fixes. Pre-release identifiers (e.g. 1.0.0-alpha.1) and build metadata (e.g. 1.0.0+build.42) are optional extensions.

When should I bump the major version?▼

Bump MAJOR when you introduce a breaking change — meaning existing code that depends on your package may break after upgrading. Examples: removing a public function, changing a function signature in an incompatible way, changing authentication format. For public APIs, a major bump communicates to users that they need to take care when upgrading.

When should I bump the minor version?▼

Bump MINOR when you add new functionality that is backward-compatible. Existing code should continue to work after a minor bump. Examples: adding a new optional parameter, adding a new public method, adding a new endpoint. When MINOR is bumped, PATCH resets to 0.

What is the difference between alpha, beta, and rc pre-release tags?▼

These are conventions within the semver pre-release field. alpha = early testing, may be unstable. beta = feature-complete, stabilization phase. rc (release candidate) = potentially final version pending last verification. They carry no semantic meaning within the semver spec itself — but the dot-separated numeric suffix (e.g. alpha.1, alpha.2) does affect precedence: alpha.1 < alpha.2 < beta.1 < rc.1 < 1.0.0.

Does build metadata affect version precedence?▼

No. Build metadata (the +suffix) is explicitly ignored when determining version precedence according to the semver spec. 1.0.0+build.1 and 1.0.0+build.2 have identical precedence — they are treated as the same version for dependency resolution purposes. Build metadata is typically used for CI build numbers or git SHA references.

What happens to the pre-release when I bump major, minor, or patch?▼

Bumping MAJOR, MINOR, or PATCH clears the pre-release identifier and build metadata. For example, bumping PATCH on 1.2.3-beta.4 produces 1.2.4 (not 1.2.4-beta.4). If you are in a pre-release cycle and want to promote to a release, bump the appropriate level without adding a new pre-release tag.

Share this tool: X / Twitter LinkedIn
✓ 60,000+ developers use DevPlaybook ★★★★★ 4.8 / 5 on Gumroad ✓ MIT licensed · Instant download ✓ No login required

Related Products

on Gumroad

You Might Also Need

More Free Tools

Related Articles

Enjoying this tool? Get more like it.

Weekly developer tool guides, productivity playbooks & AI tricks. Free. No spam.

DevPlaybook Pro 7 days free

Unlock AI-Powered Dev Tools

  • ⚡ AI Code Review, Doc Generator & SQL Builder
  • ⚡ All premium templates & early access
  • ⚡ Member discounts on Gumroad products
Start Free Trial →

$9/mo after trial · Cancel anytime

Want the full toolkit?

Get DevPlaybook Pro

Every template, guide, boilerplate, and automation script in one bundle. 13 premium products — grab them all at once and save big.

$79
$241 separately Save $162 (67% off)
Get DevPlaybook Pro — $79 →

MIT licensed · Instant download · No subscription

See what's included → Browse all deals →