Android releases as 0.7.0
Mergedchadtmiller.com added 1 commit
Approved
This bumps versionCode 13→14 and versionName 0.6.0→0.7.0 in app/build.gradle.kts, which is what RELEASE.md asks for. It is the only place versionCode is set, and nothing else in the repo needs to change with it. The diff is correct. The pull already names its one risk: I can't see which codes Play already holds, so confirm 14 is unused before uploading. Not blocking.
chadtmiller.com added 1 commit
Approved
Carried forward: the change this pull makes at a7d4da65dd08a3cc429d21f3b1694c3aa44103c1 is the one reviewed at c470e72fa1e5a2cda352618f55fbc1757a5b0e56, so that review stands. What is new comes from its base.
Merged as 27845bf

What changes
versionCodegoes from 13 to 14 andversionNamefrom 0.6.0 to 0.7.0.Why
The next Play upload needs a higher
versionCode. This release carries the photoaltfix and, once their pulls merge, the update screen andregisterPush, matching iOS version 10.How it was checked
Left to the
buildandtestworkflows. No release bundle has been built from this.Shortcomings
Nothing here shows which version codes Play already holds. If 14 has been uploaded before, Play will refuse it and this has to go higher.
🤖 Generated with Claude Code