docs(release): record v0.4.15 and make the versionCode bump non-optional - #181
Merged
Conversation
Two things the v0.4.15 cut got wrong were things this doc told it to do. - PUBLISHING.md step 1 said not to bother hand-bumping `android.versionCode`. That is true for Play (CI overrides it with run_number+100) and false for the two channels that carry most of the install base: F-Droid and direct APK key upgrades off versionCode, so reusing the previous one means the release is never offered to anyone who already has that code. Step 1 now lists all four places to bump plus the changelog named after the code, and step 5 adds the two channel checks (GitHub release — the source the in-app update check polls — and the F-Droid index) that were previously implied to be unnecessary. - docs/playstore.md release history: v0.4.15 at production versionCode 153, the first release to reach production from a tag push alone (#177), plus the superseded 152 from the pre-#180 tag. Co-Authored-By: Paperclip <noreply@paperclip.ing>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #180. AGE-111.
PUBLISHING.mdstep 1 told releasers not to bumpandroid.versionCode. True for Play (CI overrides it withrun_number + 100), false for F-Droid and direct-APK installs, which key upgrades off versionCode — and those are the majority of the install base. That advice is what produced the broken v0.4.15 tag. Step 1 now lists all four places to bump plus the changelog named after the code; step 5 adds the GitHub-release and F-Droid-index checks (the GitHub release is what the in-app update check polls).docs/playstore.md: v0.4.15 → production versionCode 153, rolled out 2026-08-14 17:58 UTC by tag push alone (run 31824702844,event=push -> track=production status=completed), which is ci(play): publish release tags straight to production, not internal #177 verified in the wild.