🏷️Semantic Versioning (SemVer) Calculator Documentation & Guide

Web & Developer

Calculate next Major, Minor, Patch, and Prerelease bumps according to the SemVer 2.0.0 specification. Test package dependency range rules (^, ~, *, x) to verify compatibility and prevent breaking changes.

📋How to Calculate Semantic Versions

1. Enter Base Version: Input your current release version (e.g. 2.7.0) or pick a preset scenario.
2. Review Calculated Bumps: Inspect calculated Next Patch (bug fixes), Next Minor (features), and Next Major (breaking changes) versions.
3. Test Range Rules: Enter a target version and dependency range (e.g. ^2.5.0) to test whether candidate releases satisfy the rule.

⚙️SemVer 2.0.0 Specification & Range Mechanics

Semantic Versioning uses a three-part format MAJOR.MINOR.PATCH to communicate API compatibility and risk to downstream consumers.

• Caret Ranges (^): Allows changes that do not modify the left-most non-zero element (e.g. ^1.2.3 allows 1.x.x, while ^0.2.3 allows 0.2.x).

• Tilde Ranges (~): Locks major and minor versions, allowing only patch increments (e.g. ~1.2.3 allows up to 1.2.x but rejects 1.3.0).

• Pre-1.0.0 Zero Major Semantics: In version 0.y.z, initial development is considered unstable, where minor version bumps may introduce breaking changes.

• Prerelease Notation: Hyphen-separated suffixes (e.g. -alpha.1, -rc.2) signify preview builds with lower precedence than associated normal releases.

Adheres to the official SemVer 2.0.0 specification utilized by npm, Yarn, Cargo, Go Modules, and Composer.

💡Practical Use Cases

Release Planning: Determine whether upcoming changes warrant a Patch, Minor, or Major version bump before publishing.
Dependency Audit: Verify package.json caret and tilde dependencies to prevent unexpected breaking updates.
CI/CD Automated Tagging: Calculate automated Git release tags based on conventional commit messages.

100% Client-Side Privacy Guarantee:All semantic version parsing and range calculations run strictly inside your local browser memory.