Semver Bump Calculator

Not sure whether your release is a major, minor, or patch? Enter the current version, tick what changed, and get the correct next version per semver.org rules. Free, instant, and private — generation happens in your browser.

100% Private — Runs entirely in browserInstant calculation & resultFree, no sign-up

Semver Bump Calculator

Tell it what changed and it tells you which part of the version to bump — per semver.org rules.

Enter a valid current version like 1.4.2

Why use a Semantic Versioning (SemVer) calculator for release management?

Maintaining a clear, reliable release history is essential for software libraries, web applications, microservices, and package managers like npm, PyPI, Cargo, and NuGet. Semantic Versioning (SemVer 2.0.0) provides a universal standard format—MAJOR.MINOR.PATCH—that communicates the risk and scope of code updates to developers and automated dependency management systems.

Determining the correct version bump manually can be confusing, especially when managing complex releases involving simultaneous bug fixes, new features, deprecation notices, and prerelease candidate tags. An interactive SemVer calculator eliminates human error by analyzing your change list and calculating the exact target version string compliant with the official semver.org specification.

  • Accurate Bump Logic: Automatically compute MAJOR (breaking API changes), MINOR (new backward-compatible features), and PATCH (backward-compatible bug fixes) increments based on your selected release changes.
  • Prerelease & Build Metadata Support: Seamlessly format release candidates (alpha, beta, rc) and append build metadata tags (e.g., commit SHAs or build timestamps) according to official SemVer rules.
  • 0.x Initial Development Compliance: Correctly handle unstable zero-version releases (0.y.z) where minor updates can introduce breaking changes prior to declaring a stable 1.0.0 production release.
  • Instant Visual Preview: Compare original version strings against calculated next-version outputs live as you adjust change parameters, complete with ready-to-copy version tags and git release commands.

SemVer resolution engine & specification architecture

Our Semantic Versioning calculator implements the formal grammar specified by SemVer 2.0.0. Under SemVer rules, a standard version number is expressed as three non-negative integers separated by dots (X.Y.Z). When a MAJOR version is incremented, both MINOR and PATCH must reset to 0. When a MINOR version is incremented, PATCH resets to 0.

For pre-releases, identifiers comprised of ASCII alphanumerics and hyphens are appended after a hyphen (e.g., 1.0.0-alpha.1). The calculation engine strictly enforces precedence comparison rules: pre-release versions have lower precedence than their corresponding normal version, and numeric identifiers are compared numerically while string identifiers are compared lexicographically.

Client-side security for private versioning data

Your software version numbers, package metadata, and release notes are evaluated completely inside your client web browser. No version strings or application parameters are ever uploaded to remote servers or logged in external databases.

Step-by-step guide to calculating version bumps

  1. Enter Current Version: Input your project's current release version (for example, 2.4.1) or select a starting template.
  2. Select Release Changes: Check the types of changes included in this release—such as breaking API modifications, feature additions, or bug fixes.
  3. Copy Next Version Tag: Instantly view and copy the calculated version string along with formatted git release tags and changelog headers.

Explore related developer utilities

Optimize your package publishing and version control workflow with our collection of free browser tools:NPM Script Helper for composing release scripts,Semantic Commit Helper for generating conventional commit messages,Changelog Generator for creating markdown release notes, andDiff Checker for inspecting code changes before release.

Frequently Asked Questions

  • When should I trigger a MAJOR version bump under Semantic Versioning?
    You must increment the MAJOR version when making incompatible, breaking API changes that disrupt backward compatibility for downstream consumers. This resets both the MINOR and PATCH numbers to zero, alerting users that upgrading requires explicit code modifications or migration steps.
  • What qualifies for a MINOR version bump versus a PATCH version bump?
    Increment the MINOR version when adding new, backward-compatible functionality or deprecating existing features without breaking existing code. Increment the PATCH version when shipping backward-compatible bug fixes, performance optimizations, or internal refactoring that does not alter public API signatures or behavior.
  • How do prerelease identifiers like alpha, beta, and rc work in SemVer?
    Prerelease identifiers (e.g., 1.2.0-alpha.1, 1.2.0-beta.2, 1.2.0-rc.1) appended via a hyphen signal that a version is unstable. Package managers prioritize non-prerelease versions over prerelease versions during dependency resolution, letting developers publish release candidates for public testing.
  • How does Semantic Versioning handle initial development versions under 1.0.0?
    Semantic Versioning reserves major version zero (0.y.z) for initial development. During this stage, the public API is considered unstable, and minor version increments (such as 0.1.0 to 0.2.0) may contain breaking changes without requiring a major version increment.
  • Does updating third-party project dependencies require a version bump?
    Dependency updates alone only require a version bump if they alter your package's public API or runtime behavior. If an updated dependency fixes an internal bug without breaking changes, ship a PATCH bump; if it introduces breaking changes, ship a MAJOR bump.
  • What is the difference between build metadata and prerelease tags in SemVer?
    Prerelease tags (e.g., -beta.1) affect version precedence and ordering during package installation. Build metadata appended with a plus sign (e.g., +20260724.sha.a1b2c3) provides build tracking details but is ignored by package managers when comparing version precedence.
  • Is any versioning data or repository information stored or transmitted to external servers?
    No. All semantic version calculations, prerelease parsing, and spec evaluations occur strictly inside your web browser using client-side JavaScript. Your version numbers, dependency lists, and release tags remain 100% private and secure on your local machine.
  • How do caret (^) and tilde (~) operators interpret SemVer ranges in package managers?
    The tilde operator (~1.2.3) permits patch updates up to the next minor version (>=1.2.3 <1.3.0), whereas the caret operator (^1.2.3) permits minor and patch updates that do not modify the leftmost non-zero digit (>=1.2.3 <2.0.0).
JSON Validator
Validate JSON instantly in your browser using the browser's native JSON parser plus the jsonrepair library (ISC). Clear error messages with line numbers. No uploads.
HTML Formatter
Format and beautify HTML code instantly in your browser with Prettier (the industry-standard formatter, MIT-licensed). No uploads, no sign-up, works offline.
CSS Minifier
Minify CSS in your browser with clean-css (MIT), one of the most downloaded CSS optimizers on npm. See exact byte savings. No uploads, no sign-up.
310 free tools
Instant — runs on your device
Files never uploaded
Free — no sign-up