8 janvier 2026 · 2 min
finding the perfect version naming strategy
Version names are tiny release contracts: they should reflect change clearly without asking developers to think too much.
Versioning tends to become inconsistent the moment a team has to do it manually. Some releases are patch bumps, some are marketing decisions, and some are just whatever felt right on Friday afternoon. That works until the release history needs to be read back.
I keep coming back to the same principle: the version should be derived from the work, not debated after the fact. Conventional commits are not perfect, but they provide a practical signal. A feat can map to a minor bump, a fix to a patch, and breaking changes can remain explicit.
Synton is built around that idea. The naming strategy should feel predictable, boring in the best way, and close enough to git history that every released APK can explain why it got that number.