chore(release): prep v0.1.10 — harden play vs jcenter/OOM, point recipe at v0.1.10
Some checks failed
ci / test-commons-core (push) Successful in 56s
ci / analyze (push) Successful in 1m47s
site / deploy (push) Successful in 34s
ci / test-app-seeds (push) Has been cancelled

- play job: apply the same two fixes the fdroid recipe uses (strip
  flutter_tesseract_ocr's dead-jcenter buildscript; cap Gradle heap to
  -Xmx4g + no daemon) so a cold-cache production AAB build can't hit
  either blocker. play builds the AAB directly, not via the recipe, so
  it was still exposed.
- pubspec: 0.1.9+11 -> 0.1.10+12.
- fdroid recipe: versionName 0.1.10, versionCodes 121/122/123,
  commit v0.1.10, CurrentVersion(Code) 0.1.10/123. binary: uses %v so
  it resolves to the v0.1.10 release assets the tag build will upload.

The v0.1.10 tag is intentionally NOT cut here: cutting it deploys to
Google Play PRODUCTION (100%) and uploads the 3 signed reference APKs.
This commit is contained in:
vjrj 2026-07-21 19:12:11 +02:00
parent e4c62f2b56
commit 1b439e9499
3 changed files with 19 additions and 12 deletions

View file

@ -61,6 +61,13 @@ jobs:
working-directory: apps/app_seeds
run: |
flutter pub get
# Same two hardenings the fdroid recipe applies (this job builds the AAB
# directly, not via the recipe, so a cold cache is still exposed):
# 1) strip flutter_tesseract_ocr's dead-jcenter buildscript (AGP 7.1.2) so
# it inherits the app's AGP instead of hitting jcenter.bintray.com;
# 2) cap the Gradle heap so the build fits the shared CI host's RAM.
find "${PUB_CACHE:-$HOME/.pub-cache}" -path '*flutter_tesseract_ocr-*/android/build.gradle' -exec sed -i '/^buildscript {/,/^}/d' {} +
printf 'org.gradle.jvmargs=-Xmx4g -XX:MaxMetaspaceSize=1g\norg.gradle.daemon=false\n' >> android/gradle.properties
dart run slang
dart run build_runner build --delete-conflicting-outputs