Merge pull request 'ci(release): trim setup-android, drop broken Gradle cache, add job timeout' (#13 ) from ci/release-workflow-speedup into main

Reviewed-on: #13 Reviewed-by: Colby Whitlock <whitlocktech@gmail.com>
ci(release): fix workflow file mangled by prior base64 double-encode
2026-07-20 17:50:25 +00:00 · 2026-07-20 17:39:29 +00:00 · 2026-07-20 17:37:15 +00:00 · 2026-07-20 09:35:19 +00:00 · 2026-07-20 04:31:05 -05:00 · 2026-07-20 09:17:23 +00:00
1 changed files with 10 additions and 11 deletions
--- a/.gitea/workflows/release.yml
+++ b/.gitea/workflows/release.yml
@@ -57,6 +57,10 @@ env:
 jobs:
  release:
    runs-on: ubuntu-latest
+    # Fail fast on a genuinely wedged run (e.g. a stalled SDK/network download on
+    # the self-hosted runner) instead of hanging forever and — because concurrency
+    # is `cancel-in-progress: false` — blocking every later release behind it.
+    timeout-minutes: 30
    # Don't loop on our own bump commit (belt-and-suspenders with [skip ci]).
    # Quoted because the expression contains a colon (`chore(release):`), which an
    # unquoted YAML scalar would misparse as a mapping value.
@@ -149,6 +153,12 @@ jobs:
      - name: Set up Android SDK
        if: ${{ steps.plan.outputs.release == 'true' }}
        uses: android-actions/setup-android@v3
+        with:
+          # Only put cmdline-tools on PATH. The action's default package set drags in
+          # the whole emulator + the legacy `tools` package (hundreds of MB, network-
+          # bound on this runner) that a headless APK build never uses. The next step
+          # installs exactly the packages we need.
+          packages: ''

      - name: Install Android SDK packages
        if: ${{ steps.plan.outputs.release == 'true' }}
@@ -156,17 +166,6 @@ jobs:
          set +o pipefail
          yes | sdkmanager "platform-tools" "platforms;android-35" "build-tools;35.0.0"

-      - name: Cache Gradle
-        if: ${{ steps.plan.outputs.release == 'true' }}
-        uses: actions/cache@v4
-        with:
-          path: |
-            ~/.gradle/caches
-            ~/.gradle/wrapper
-          key: gradle-${{ runner.os }}-${{ hashFiles('**/*.gradle.kts', 'gradle/libs.versions.toml', 'gradle/wrapper/gradle-wrapper.properties') }}
-          restore-keys: |
-            gradle-${{ runner.os }}-
-
      - name: Decode signing keystore
        if: ${{ steps.plan.outputs.release == 'true' }}
        env:
Author	SHA1	Message	Date
Colby Whitlock	0c395b2527	Merge pull request 'ci(release): trim setup-android, drop broken Gradle cache, add job timeout' (#13 ) from ci/release-workflow-speedup into main Some checks failed Release APK / release (push) Failing after 9m23s Details Reviewed-on: #13 Reviewed-by: Colby Whitlock <whitlocktech@gmail.com>	2026-07-20 17:50:25 +00:00
claude	2d84a930e5	ci(release): fix workflow file mangled by prior base64 double-encode All checks were successful PR Checks / android-build (pull_request) Successful in 10m19s Details Restore proper YAML content (the previous commit on this branch accidentally stored the base64 string as the literal file body).	2026-07-20 17:39:29 +00:00
claude	b6a0fa1f5d	ci(release): trim setup-android, drop broken Gradle cache, add job timeout All checks were successful PR Checks / android-build (pull_request) Successful in 20m43s Details 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
Colby Whitlock	bc09593550	Merge pull request 'ci(release): conventional-commit auto-release engine for the APK' (#12 ) from ci/android-release-engine into main Some checks failed Release APK / release (push) Has been cancelled Details Reviewed-on: #12 Reviewed-by: Colby Whitlock <whitlocktech@gmail.com>	2026-07-20 09:35:19 +00:00
wtclaude	9514172b71	ci(release): auto-release engine (conventional commits) for the APK Replace the tag-triggered release.yml with link/'s language-agnostic release engine, adapted for Android. On every push to main it derives the next version from conventional-commit subjects since the last v* tag (feat!/BREAKING -> major, feat -> minor, fix\|perf -> patch; nothing releasable -> no release), generates a grouped changelog, bumps versionName in build.gradle.kts (versionCode derived major10000+minor100+patch, monotonic), builds the SIGNED release APK, then commits the bump [skip ci], tags vX.Y.Z, and creates the Gitea release with the notes + APK + SHA256SUMS. Uses REGISTRY_USER/REGISTRY_TOKEN (write:repository) to push the bump + create the release, matching link/. main must allow that account to push (bump lands on main; the [skip ci] + head-commit guard prevent a re-trigger loop). Signing secrets (ANDROID_KEYSTORE_BASE64/_PASSWORD, ANDROID_KEY_ALIAS/_PASSWORD) unchanged. Same self-hosted-runner handling as pr-checks.yml (apt JDK 17, sdkmanager, chmod). Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-20 04:31:05 -05:00
Colby Whitlock	de79bf547c	Merge pull request 'feat(release): m6 release mechanics — signed APK, R8, version guard, icons' (#11 ) from feat/m6-release into main Reviewed-on: #11 Reviewed-by: Colby Whitlock <whitlocktech@gmail.com>	2026-07-20 09:17:23 +00:00