Software Version / Package Tools

Version Increment Generator

See the next patch, minor, major and prerelease version for any semantic version, with the matching npm version command.

Enter your current version (and optionally a prerelease name such as beta or rc) to see every possible next version side by side.

Current version

Prerelease identifier (optional)

A leading v is accepted and dropped. Build metadata (+...) is removed from the result, as npm version does.

More Software Version / Package Tools

View all 9

Version Comparator npm Package Version Checker SemVer Validator Composer Version Constraint Helper Version Range Calculator Python Requirements Version Helper Package Name Validator Dependency Version Comparator

Tag the chosen release with the Git Tag Generator, and record it in your changelog.

What Is the Version Increment Generator?

It calculates the next version for each kind of release using the same rules as npm version and the node-semver library, so the result matches what your tooling would produce.

When to Use It

Deciding the next release number after a fix, a new feature or a breaking change.
Starting a beta or release-candidate cycle (2.0.0-rc.0, 2.0.0-rc.1...).
Checking what a release script will produce before running it.

How to Use It

Enter the current version, e.g. 1.4.2.
Optionally enter a prerelease identifier such as beta.
Copy the version you need from the table.

Examples

1.4.2 → patch 1.4.3, minor 1.5.0, major 2.0.0.
1.4.2 with beta → premajor 2.0.0-beta.0.
2.0.0-beta.3 → prerelease 2.0.0-beta.4, major 2.0.0 (finishing the prerelease, not 3.0.0).

Understanding the Result

A normal bump resets the lower numbers to zero. When the current version is already a prerelease of the target, "major", "minor" or "patch" simply drops the prerelease tag - the release you were testing becomes final. Build metadata is removed from every result.

Limitations

This tool only calculates version numbers; it does not edit package.json or create tags. Choosing between major, minor and patch depends on your changes - if you are unsure whether a change is breaking, treat it as major. To assemble a version from custom parts instead, use the Semantic Version Generator; to check the result, use the SemVer Validator.