Semver Toolkit
Compare semantic versions and suggest the next bump level.
Comparing and bumping semantic versions
Semantic versioning communicates breaking changes through major bumps, backward-compatible features through minor bumps, and fixes through patches. Compare tools order versions correctly across pre-release tags like 1.0.0-beta.2 and build metadata.
Pre-release versions sort before their release counterparts. Ignoring build metadata (+sha) is correct for ordering but may matter for artifact registries that treat + segments as unique keys. Align bump suggestions with your Git tag policy and changelog automation.
Libraries consumed as ranges (^1.2.0) still need explicit major bumps when removing public APIs. Use compare output in CI to block accidental downgrades or duplicate tags during monorepo releases.
Check versions locally when coordinating private package feeds. Comparison does not leak package names to servers when run entirely client-side.
Reference Guide
DevOps tool - all processing runs locally in your browser. No data is sent to a server.
Operation: semver-compare
Paste input, click Run, and copy the result. For two-input tools, fill both fields before running.
Example Input
1.2.3 1.2.4
A sample loads automatically when you open this tool. Use Load Sample to reset it.