Skip to content

chore: open 2.02 dev cycle - #53

Merged
criticalAY merged 1 commit into
masterfrom
chore/open-2.02-dev-cycle
Aug 9, 2026
Merged

chore: open 2.02 dev cycle#53
criticalAY merged 1 commit into
masterfrom
chore/open-2.02-dev-cycle

Conversation

@criticalAY

@criticalAY criticalAY commented Aug 8, 2026

Copy link
Copy Markdown
Owner

Post-release bump of the fallback version, following the same shape as a1ce0db ("chore: open 2.01 dev cycle").

- versionCode = overrideVersionCode ?: 20100001
- versionName = overrideVersionName ?: "2.01.00dev"
+ versionCode = overrideVersionCode ?: 20200001
+ versionName = overrideVersionName ?: "2.02.00dev"

Beyond the routine bump, 20100001 is now actively harmful as a default: an Android Studio build picked it up and got as far as a Play upload, which Play rejected with "Version code 20100001 has already been used". Any local bundleRelease would keep producing something Play refuses, and it silently disagrees with the 20100300 that 2.01.00 actually shipped as.

Verified: a plain :app:assembleDebug with no -P flags now reports versionCode='20200001' versionName='2.02.00dev-debug'.

Bumps the fallback version used by any build that does not go through the
release workflow. Beyond following the usual post-release bump, 20100001 is
now unusable: an Android Studio build picked up that default and was uploaded
to Play, so Play rejects it with "Version code 20100001 has already been
used". Leaving the default pointing at a consumed code means every local
bundleRelease produces something Play refuses.
@criticalAY
criticalAY merged commit f1933c7 into master Aug 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant