What's patched, minor, and major?

Patch: backwards-compatible bug fix (1.2.3 → 1.2.4). Minor: backwards-compatible feature (1.2.3 → 1.3.0). Major: breaking change (1.2.3 → 2.0.0).

What about pre-release?

Adds -alpha.1, -beta.1, -rc.1 suffixes. 1.2.3 → 1.2.4-alpha.1. Pre-releases sort before the final version per semver spec.

Yes — the +buildid suffix. 1.2.3+20240101 is 'version 1.2.3, built on 2024-01-01'. Build metadata is ignored for version precedence.

Yes — matches npm's behavior exactly. 0.x.y has special rules (x is major, y is minor+patch). Toggle between strict semver and npm rules.

A worked example, rendered from real sample data. Sign in to run the tool on your own input.

Input

{"version":"1.2.3","bumpType":"patch","suffix":"none"}

Output

Current: 1.2.3 (stable)
Bump Type: patch
Suffix: none

Next Version: 1.2.4

Compute next major / minor / patch / prerelease. Part of the DevTools Surf developer suite. Browse more tools in the Developer Utilities collection.

Semantic Versioning (SemVer) was created by Tom Preston-Werner, co-founder of GitHub, and formalized in the SemVer 2.0.0 specification in 2013.
The SemVer spec states that version 0.y.z is for initial development and anything may change at any time — the public API should not be considered stable.
npm adopted SemVer as its versioning standard from the very beginning, and the ~ and ^ range operators in package.json are SemVer-aware.

What's patched, minor, and major?: Patch: backwards-compatible bug fix (1.2.3 → 1.2.4). Minor: backwards-compatible feature (1.2.3 → 1.3.0). Major: breaking change (1.2.3 → 2.0.0).
What about pre-release?: Adds -alpha.1, -beta.1, -rc.1 suffixes. 1.2.3 → 1.2.4-alpha.1. Pre-releases sort before the final version per semver spec.
Does it support build metadata?: Yes — the +buildid suffix. 1.2.3+20240101 is 'version 1.2.3, built on 2024-01-01'. Build metadata is ignored for version precedence.
Is this compatible with npm?: Yes — matches npm's behavior exactly. 0.x.y has special rules (x is major, y is minor+patch). Toggle between strict semver and npm rules.

A worked example, rendered from real sample data. Sign in to run the tool on your own input.

Input

{"version":"1.2.3","bumpType":"patch","suffix":"none"}

Output

Current: 1.2.3 (stable)
Bump Type: patch
Suffix: none

Next Version: 1.2.4

Compute next major / minor / patch / prerelease. Part of the DevTools Surf developer suite. Browse more tools in the Developer Utilities collection.

Semantic Versioning (SemVer) was created by Tom Preston-Werner, co-founder of GitHub, and formalized in the SemVer 2.0.0 specification in 2013.
The SemVer spec states that version 0.y.z is for initial development and anything may change at any time — the public API should not be considered stable.
npm adopted SemVer as its versioning standard from the very beginning, and the ~ and ^ range operators in package.json are SemVer-aware.

What's patched, minor, and major?: Patch: backwards-compatible bug fix (1.2.3 → 1.2.4). Minor: backwards-compatible feature (1.2.3 → 1.3.0). Major: breaking change (1.2.3 → 2.0.0).
What about pre-release?: Adds -alpha.1, -beta.1, -rc.1 suffixes. 1.2.3 → 1.2.4-alpha.1. Pre-releases sort before the final version per semver spec.
Does it support build metadata?: Yes — the +buildid suffix. 1.2.3+20240101 is 'version 1.2.3, built on 2024-01-01'. Build metadata is ignored for version precedence.
Is this compatible with npm?: Yes — matches npm's behavior exactly. 0.x.y has special rules (x is major, y is minor+patch). Toggle between strict semver and npm rules.