Git & GitHub Tools

Semantic Version Generator

Assemble a valid SemVer version from major, minor, patch, prerelease, and build metadata.

Enter major, minor, and patch numbers, and optionally a prerelease or build metadata label - this tool assembles a valid SemVer string and explains it.

Start from an existing version (optional)

Splits a version into its parts below. To bump it, use the Version Increment Generator.

Major

Minor

Patch

Prerelease (optional)

Build Metadata (optional)

More Git & GitHub Tools

View all 18

Git Tag Generator Changelog Generator GitHub Actions Cron Helper README Generator GitHub Actions Validator Git Command Generator GitHub Actions YAML Generator Git Command Builder

Pair this with the Git Tag Generator to turn the resulting version into a properly formatted release tag.

What Is Semantic Versioning?

Semantic Versioning (SemVer) is a widely-used convention for version numbers in the form MAJOR.MINOR.PATCH, where major versions signal breaking changes, minor versions add backward-compatible functionality, and patch versions are backward-compatible bug fixes. Optional prerelease (-beta.1) and build metadata (+build.5) suffixes can be appended.

Why Use This Tool?

Correctly incrementing and formatting a SemVer string - especially with prerelease and build metadata - has specific rules (e.g. prerelease versions have lower precedence than the associated normal version). This tool assembles a syntactically valid string and explains what each part means.

How to Use It

Enter the major, minor, and patch numbers.
Optionally add a prerelease label (e.g. beta.1, rc.2).
Optionally add build metadata (e.g. build.20240115).
Copy the assembled version string.

Understanding the Result

The explanation breaks down what each segment communicates to consumers of your package - for example, whether it's safe to upgrade automatically based on the major version being unchanged.

Frequently Asked Questions

Whenever you make a change that breaks backward compatibility for users of your package or API. New features go in a minor release and bug fixes in a patch release.

It is a prerelease of 1.0.0. Prereleases are considered unstable and sort before the final release, so 1.0.0-beta.1 < 1.0.0.

No. Build metadata after "+" (for example +build.42) is informational only and is ignored when versions are compared.