Developer

Semantic Version Calculator

Estimate the right patch, minor, or major version bump from release notes before you tag or publish a package.

Current versionmajor.minor.patch
Release notesWhat changed
Recommended3.0.0
Patch2.4.2
Minor2.5.0
Major3.0.0
Recommendationmajor bump
Use a major bump when consumers are likely to change code or configuration to adopt this release.

Detected breaking-change language in the notes.

Recommendation logic

The recommendation is heuristic-based. It looks for feature and breaking-change language so teams can get a fast gut check before a real release review.

Use this tool when

These are the practical situations where this workflow usually earns its keep.

You need to reason about version bumps with clearer semver language.

You want a browser-local pass before documenting the intended version change consistently across the workflow.

You need a smaller, cleaner review surface during release planning and package review.

Daily workflow acceleration

Semantic Version Calculator helps when teams need to reason about version bumps with clearer semver language without opening a heavier system or rebuilding the same transformation manually every time.

Review and handoff clarity

A focused output is useful when the next step is documenting the intended version change consistently across the workflow and the current raw input would otherwise slow down the reviewer or teammate.

Lower-friction local handling

For release planning and package review, keeping the task in the browser is helpful because the source material often does not need to leave the user’s machine just to answer this one question.

Common mistakes to avoid

These are the checks that usually keep the output useful instead of misleading.

A semver recommendation is still a judgment call that depends on the real behavioral impact of the change.

Using a summary as a substitute for reading the source artifact when the change is high risk.

Forgetting that generated snippets and reviews may need project-specific edits before use.

Learn how to use this tool

Estimate patch, minor, and major bumps from release notes and compatibility signals. This guide focuses on how teams use it for release planning and package review when the real job is to reason about version bumps with clearer semver language.

Read the guide

Tell us what is missing

If this flow helped only partly, leave feedback so we can understand the missing step or edge case.

Leave feedback

Request the next tool

Use the wishlist to suggest the next utility, workflow, or improvement that would complete this job to be done.

Open wishlist

Related tools

These tools often appear right before or right after this workflow.