SemVer Release Advisor
Decide the exact next version from your release changes
What is the SemVer Release Advisor?
The SemVer Release Advisor turns a changelog or Conventional Commits into an explainable major, minor, patch, prerelease, or no-release recommendation. It evaluates compatibility of the declared public contract, not ticket size or QA effort, and calculates the exact next version.
How to decide the next version
Enter the current strict Semantic Version, choose the project type and policy, then paste one change per line. Review only the ambiguous items. A backward-incompatible public change requires major, compatible public functionality requires minor, a compatible correction requires patch, and internal-only work can require no release.
SemVer rules and 0.x projects
For stable 1.x and later releases, the highest-impact included change wins. SemVer does not define a universal bump mapping for initial-development 0.x versions, so the tool keeps strict impact separate from the visible Pragmatic 0.x policy. Prerelease channels are applied after the target stable bump is known.
Conventional Commits, ranges, and privacy
feat seeds a minor suggestion, fix seeds patch, and ! or BREAKING CHANGE seeds major; every suggestion stays editable. Secondary utilities validate, compare, increment, and check npm-compatible ranges with the official semver package. All source text stays in the browser and is not persisted unless you explicitly opt in.
Frequently asked questions
Does E2E testing determine the bump? No; testing effort is release risk, not SemVer impact.
Is v1.2.3 strict SemVer? No; it is accepted as a common tag and normalized to 1.2.3.
Does build metadata affect precedence? No.
Is deprecation major? Announcing deprecation while keeping functionality is minor; removal is major.
