EasySemVer
Your version number is a fact, not a vote.
EasySemVer works out what your next version number is from what actually changed in your code, and writes it into every place a version already lives in your code. Nobody decides the number. Nobody has to remember to bump it.
Free under the MIT licence. No limit on repositories, builds, or people.
What it does
A removed method is Major because it is Major, on the run that removed it.
EasySemVer reads the public API of everything in a folder — C# projects, SwiftPM targets, Xcode targets — compares it against the last run, and takes the highest impact it finds.
- Major — something a caller relied on stopped working.
- Minor — something was added.
- Patch — everything else.
Roughly eighty rules sit behind those three lines, and each one speaks its own language: adding a case to a public Swift enum is Major, because a client switching exhaustively over it stops compiling. Adding a member to a C# enum is Minor, because C# has no such requirement.
Why it's different
Most versioning tools ask a human to label the change and then trust the label. A feat: prefix, a BREAKING CHANGE: footer, a changeset file — all of it is someone's recollection of what they did, written at the end of a long day.
EasySemVer doesn't ask. It reads the code from source rather than from compiled assemblies, so it works before your build has run, and every verdict names the rule and the exact symbol behind it. A release explains itself.
There is no configuration file. There is nothing to tune.
Free, and staying that way
Add two steps to a GitHub Actions workflow and the repository versions, commits and tags itself. Or install the CLI and call it from whatever runs your release. Same tool either way.
MIT licensed. Use it in production, use it commercially, use it across a thousand repositories. We're not counting, and we're not going to start.
What isn't free
Support and new capability are the business. If you need EasySemVer to hold up something that matters, that's the conversation to have with us:
A response time you can put in a document. A named support commitment, an escalation path, and engineers who wrote the rules answering the ticket.
Features you need that we haven't built. Another language, another version location, a rule your codebase requires, an integration with the CI system you actually run. The price is not based on your repositories, your build minutes, or your headcount. It is based on the SLA you want and the features you need — and nothing else.
Where to get it
Need more?
Start free. Talk to us when it matters.
The tool costs nothing to try on a real repository this afternoon. When you need a support commitment behind it, or something built that isn't there yet, tell us what you need.