Dev
Générateur de versions Semver aléatoires
A random semver version generator produces valid semantic version numbers — the MAJOR.MINOR.PATCH format that npm, Cargo, and most package managers expect. It is built for developers who need realistic version strings to test release scripts, changelog tooling, version-comparison logic, or sort order without hand-typing dozens of plausible numbers. Toggle pre-release tags on to get values like 2.4.0-beta.1 and confirm your code orders pre-releases correctly against stable releases. Every value follows the SemVer specification, so it slots straight into fixtures, mock registries, and documentation. Generate a batch, copy the list, and feed it into whatever parses or compares versions in your project. In practice, people reach for it for tasks like verifying changelog and release-automation tooling, documentation examples that need plausible version numbers. Everything runs instantly in your browser — it is free, needs no sign-up, and has no usage limits.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Set how many version numbers you need for your test or fixture.
- Toggle pre-release tags on if you want values like 1.2.0-beta.3 in the mix.
- Click Generate to produce the list of valid SemVer strings.
- Copy the whole batch into your test fixture, mock registry, or documentation.
Use Cases
- •Testing version-comparison and sort logic against many realistic inputs
- •Seeding a mock package registry or release history
- •Verifying changelog and release-automation tooling
- •Fixtures for tests that parse or validate SemVer strings
- •Documentation examples that need plausible version numbers
Tips
- →Enable pre-release tags specifically when testing sort order — that is where most version bugs surface.
- →Generate a large batch to stress-test how your parser handles two- and three-digit components.
- →Pair with a changelog or commit generator to build a realistic release history.
- →For production version bumps, derive the number from your actual release process rather than a random tool.
FAQ
what is semantic versioning
Semantic versioning (SemVer) is a convention of MAJOR.MINOR.PATCH, where MAJOR marks breaking changes, MINOR adds backward-compatible features, and PATCH covers backward-compatible fixes. An optional pre-release tag like -beta.1 marks an unstable build that sorts before the matching stable release.
are the generated versions valid semver
Yes. Every value follows the SemVer format, including optional pre-release identifiers when you enable them, so they parse cleanly in libraries like node-semver and pass validation in package tooling.
why include pre-release tags
Pre-release tags such as -alpha, -beta, and -rc are where version-ordering bugs hide, because they must sort before the stable version. Enable them to confirm your comparison logic handles 2.0.0-rc.1 < 2.0.0 correctly.
What do the three numbers in a semver version mean?
In MAJOR.MINOR.PATCH, you bump MAJOR for breaking changes, MINOR for new backwards-compatible features, and PATCH for backwards-compatible bug fixes — so 2.4.1 is the second major line, fourth feature update, first patch. The generator produces valid versions in this format (with optional pre-release tags), ideal for testing release tooling, sorting logic, and changelog generators.
What is the difference between a pre-release and build metadata?
A pre-release tag (1.0.0-beta.1) marks an unstable version that sorts before the final release, while build metadata (1.0.0+20130313) is appended after a plus sign and is ignored when comparing precedence. The generator can include pre-release tags, so you can verify your version-parsing and ordering code handles them correctly rather than only plain release numbers.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.