Pick the change type and get the next version
Enter the current version and the kind of change this release carries, and the page builds the next version string. A breaking change bumps the major number, a backward compatible feature the minor and a bug fix the patch: those are the increments SemVer 2.0.0 defines itself. Every result also states whether the increment comes from the specification or from convention.
Two spots deserve care. First, a prerelease sorts below the release with the same numbers, so the next release after 1.0.0-rc.1 is 1.0.0 and not 1.0.1. Second, the specification designates 0.y.z as initial development and guarantees no compatibility there, so whether a breaking change moves to 1.0.0 or stays on 0.y is a convention, offered here as a choice. Current as of October 2026.
Build metadata is ignored for precedence and dropped from the next version, so re-attach it yourself if you need it. How a prerelease identifier is incremented is also undefined, so the widely used approach of bumping the last numeric identifier is applied. Parsing version ranges or comparing two ranges is not supported.
Frequently Asked Questions
It is 1.0.0. A prerelease sorts below the release with the same numbers, so dropping the identifier is itself the next release. It is not 1.0.1 from a patch bump.
Both are in use because the specification does not decide. Pick 1.0.0 if you are ready to declare stability, or 0.5.0 to continue initial development. Switch the selector to compare the two results.
No. Build metadata is ignored for precedence and this page drops it from the next version, so re-attach it yourself if you need it.