Yonto Player ships often, and an Android install updates only when the new APK meets the platform's rules. So the way I version and cut a release is…

Yonto Player ships often, and an Android install updates only when the new APK meets the platform's rules. So the way I version and cut a release is a short list of rules, each one with a reason behind it. This is the list. It is not clever, and that is the point of it. One version pair, in one file Every app module reads its version from a single pair in gradle.properties.

This is a simplified sketch of it, with made-up numbers and generic names: # gradle.properties (simplified sketch, made-up numbers) # The release's version, read by every app module. app.versionCode=12 app.versionName=1.4.2 versionName is what people read: semantic, MAJOR.MINOR.PATCH, and the git tag is v plus it. versionCode is what Android reads. The TV app and the phone app both take the same pair, so a release bumps both at once and the two stay in step.

PATCH goes up by one on every release The usual bump is PATCH, by exactly one. A release is usually a fix or a polish, and it should look small in the version too. MINOR and MAJOR move only when I decide a release marks a step, and each one resets the parts below it to zero. A change that merely feels big does not move them. The plugin contract has a version of its own, and it does not shape the app's version.

They answer different questions, so each keeps its own number. A version code that only goes up Android requires the versionCode of an update to be higher than the installed one. So the code goes up by one on every release, whatever part of the name moved. It is a counter and not a value computed from the name. The next release is always the last one plus one, and the name can follow whatever semantic rules it likes.

A patch that must not carry main Sometimes the fix has to go out without the rest of main.

Source disclosure

This is a source-linked briefing. Read the original report from Dev Community .