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.
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.
Related Products
on GumroadDeveloper Productivity Bundle
Stop rebuilding the same setup every project. 51 VSCode snippets, 40 Git aliases, 5 Docker Compose stacks, 5 GitHub Actions workflows, 5 README templates, and a dotfiles kit. Set up a professional dev environment in under an hour.
Buy on Gumroad →Developer Cheat Sheet Bundle
10 print-ready cheat sheets for the tools developers use every day: Git, Docker, Linux CLI, SQL, Regex, HTTP Status codes, VS Code shortcuts, Bash scripting, jq/JSON, and Markdown.
Buy on Gumroad →DevToolkit Starter Kit
A ready-to-deploy developer tools website with 12 built-in tools. Astro + Preact + Tailwind. Deploy to Cloudflare Pages for free. Built-in SEO, dark mode, and ad-ready layout.
Buy on Gumroad →You Might Also Need
Git Stash Manager
Visual reference for git stash commands. Copy-ready stash push, pop, apply, drop, list, and branch commands with stash index control. Free git stash cheat sheet.
Open free tool →
npm Package Stats
Look up npm package weekly download counts, unpacked size, dependency count, latest version, license, and repository link. Live data from the npm registry.
Open free tool →
Git Cheatsheet Interactive
Searchable, interactive Git cheatsheet with 50+ commands. Filter by category, copy commands instantly. Covers setup, staging, branching, remotes, history, undo, and tags. Free.
Open free tool →
More Free Tools
Related Articles
Conventional Commits and Commitlint: Complete Guide 2026
Master Conventional Commits and commitlint to automate changelogs, semantic versioning, and release workflows. Covers setup, configuration, CI/CD integration, and the full commitlint toolchain with real .commitlintrc examples.
Aider AI: The Ultimate Terminal-Based AI Coding Assistant for 2026
Complete guide to Aider AI coding assistant. Setup, best practices, model options, and how this terminal-based tool compares to GUI editors for serious developer workflows.
Changesets vs Semantic Release vs Release Please: Monorepo Release Automation 2026
Automated versioning and changelog generation for monorepos in 2026. Deep comparison of Changesets, Semantic Release, and Release Please — covering CI/CD integration, GitHub Actions workflows, and which tool fits your team.
Lefthook vs Husky vs pre-commit: Git Hooks Manager Comparison 2026
Which git hooks manager should you use in 2026? We compare Lefthook, Husky, and pre-commit on speed, parallel execution, cross-platform support, and monorepo ergonomics with real configuration examples.
Monorepo Tools Compared: Turborepo vs Nx vs Moon 2026
In-depth comparison of the top monorepo tools for 2026: Turborepo, Nx, Moon, and Rush. Compare setup, caching, task orchestration, CI integration, and benchmarks to pick the right tool for your team.
Enjoying this tool? Get more like it.
Weekly developer tool guides, productivity playbooks & AI tricks. Free. No spam.
Unlock AI-Powered Dev Tools
- ⚡ AI Code Review, Doc Generator & SQL Builder
- ⚡ All premium templates & early access
- ⚡ Member discounts on Gumroad products
$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.
MIT licensed · Instant download · No subscription
See what's included → Browse all deals →