Semver Calculator

The caret (^) allows changes that do not modify the left-most non-zero digit, meaning it allows minor and patch updates but not major updates. For example, ^1.2.3 allows versions from 1.2.3 to less than 2.0.0. The tilde (~) allows only patch-level changes, so ~1.2.3 allows versions from 1.2.3 to less than 1.3.0.

Prerelease versions use suffixes like -alpha, -beta, or -rc followed by optional numbers (e.g., 1.0.0-beta.1). They indicate unstable versions still under development. Prerelease versions have lower precedence than the normal version, so 1.0.0-alpha comes before 1.0.0. Use them to distribute early versions for testing.

Version comparison follows a left-to-right precedence. First the major versions are compared, then minor, then patch. If these are equal, prerelease versions are compared alphabetically and numerically. Build metadata (after the + sign) is ignored in comparisons. For example, 2.0.0 is greater than 1.9.9 and 1.0.0 is greater than 1.0.0-beta.

Prerelease identifiers (after the hyphen) affect version precedence and indicate unstable releases. Build metadata (after the plus sign) provides additional information like build numbers or commit hashes but is completely ignored during version comparison. For example, 1.0.0+build.123 is equal to 1.0.0+build.456 in terms of precedence.

Enter a version range using npm-style syntax and a list of versions to test. The tool shows which versions satisfy the range and which do not. It also identifies the minimum and maximum satisfying versions. This is useful for understanding dependency resolution and checking package compatibility.

Increment MAJOR when you make incompatible API changes that require users to modify their code. Increment MINOR when you add functionality in a backward compatible manner. Increment PATCH when you make backward compatible bug fixes. Following these rules helps users understand the risk of updating to a new version.