Report

Help us improve this tool

Semver Bump

Bump major, minor, patch, or prerelease on a semver string using npm semver rules.

O M T

Bump semantic versions for releases and changelogs

Release pipelines and package maintainers increment Semantic Versioning numbers when shipping features, fixes, or breaking changes. Given a current version such as 1.2.3, this tool computes the next major, minor, patch, and prerelease strings using the same rules as the npm semver library.

Prerelease identifiers

Pre-major, pre-minor, pre-patch, and prerelease bumps accept a custom identifier (for example alpha or rc). That matches how Node packages publish 2.0.0-alpha.0 lines before a stable tag.

Pair results with the Semver Comparator when you need ordering or range satisfaction checks before tagging.

Frequently Asked Questions

What happens when I bump major on 1.2.3?

A major bump resets minor and patch to zero, producing 2.0.0 for a stable release line.

Does this accept build metadata?

Versions with +build metadata are parsed when valid semver. Bump results follow npm semver precedence rules for the core version.

Is anything sent to a server?

All bump math runs in your browser. Versions you type are not uploaded.