claude b6a0fa1f5d ci(release): trim setup-android, drop broken Gradle cache, add job timeout ...

The release workflow was slow and sometimes appeared to hang mid-build:

- android-actions/setup-android@v3 pulled the entire Android emulator and the
  legacy `tools` package (hundreds of MB, network-bound on the self-hosted
  runner) that a headless APK build never uses. Pin `packages: ''` so it only
  puts cmdline-tools on PATH; the next step installs exactly what we need.
- The `actions/cache@v4` Gradle step timed out every run against the Gitea
  artifact-cache backend (`getCacheEntry failed: Request timeout`), adding
  latency with no benefit. Dropped it.
- The job had no timeout, and with `concurrency.cancel-in-progress: false` a
  genuinely wedged run would hang forever and block every later release behind
  it. Added `timeout-minutes: 30` so a hang fails fast.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-07-20 17:37:15 +00:00

..

pr-checks.yml

ci(android): raise Gradle heap + scope PR gate to debug variant

2026-07-19 17:51:08 -05:00

release.yml

ci(release): trim setup-android, drop broken Gradle cache, add job timeout

2026-07-20 17:37:15 +00:00