From 601088b5c667934e5a7147f094fa1fcb0d129e09 Mon Sep 17 00:00:00 2001
From: Tommy Chow <tommyxchow@gmail.com>
Date: Sat, 8 Aug 2026 16:04:15 -0700
Subject: [PATCH] ci: bump ruby to 3.3 and report scheduled dry-run failures
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

fastlane warns on every run that it will soon require Ruby 3.3.0 or
newer; both release workflows pinned 3.2. Bumping now means that break
lands on a quiet commit instead of mid-release. fastlane 2.234 already
supports 3.3 and no gem in either lockfile is version-sensitive, so this
stands alone — the lockfiles are unchanged.

Also gives the weekly dry-run somewhere to report. It broke on the
release after 5.1.0 and stayed red for weeks without surfacing, which is
the failure mode of any heartbeat nobody reads: it looks green by
default. Scheduled failures now open a tracking issue, or comment on the
existing one for each week it stays red. Dispatched runs are excluded —
those are already in front of whoever started them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 .github/workflows/release-dryrun.yml | 51 ++++++++++++++++++++++++++--
 .github/workflows/store-release.yml  |  4 +--
 2 files changed, 51 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/release-dryrun.yml b/.github/workflows/release-dryrun.yml
index fd6d0c2d..3400ab27 100644
--- a/.github/workflows/release-dryrun.yml
+++ b/.github/workflows/release-dryrun.yml
@@ -39,7 +39,7 @@ jobs:
       - name: Set up Ruby and Bundler
         uses: ruby/setup-ruby@v1
         with:
-          ruby-version: 3.2
+          ruby-version: 3.3
           bundler-cache: true
 
       # Setup Java so that we can build the appbundle.
@@ -106,7 +106,7 @@ jobs:
       - name: Set up Ruby and Bundler
         uses: ruby/setup-ruby@v1
         with:
-          ruby-version: 3.2
+          ruby-version: 3.3
           bundler-cache: true
 
       # Setup and cache Flutter to install packages and build.
@@ -124,3 +124,50 @@ jobs:
       # fully signed archive without uploading to the App Store.
       - name: Sign and build with fastlane (no publish)
         run: cd ios && bundle exec fastlane release dry_run:true
+
+  # A heartbeat nobody reads is worse than none: it reads as green by default.
+  # This one broke on the release after 5.1.0 and stayed broken for weeks
+  # without surfacing, so scheduled failures now open a tracking issue and
+  # comment on it each week it stays red. Only on `schedule` — a failed
+  # workflow_dispatch is already in front of whoever pressed the button.
+  notify:
+    name: Report scheduled failure
+    needs: [android, ios]
+    if: failure() && github.event_name == 'schedule'
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Open or update the tracking issue
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          LABEL: release-dryrun
+          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+        run: |
+          set -euo pipefail
+
+          # Idempotent: `gh issue create --label` fails outright if the label
+          # is missing, and it won't exist on the first failure.
+          gh label create "$LABEL" \
+            --color B60205 \
+            --description "Automated: the weekly release dry-run is failing" \
+            2>/dev/null || true
+
+          existing=$(gh issue list --state open --label "$LABEL" --limit 1 \
+            --json number --jq '.[0].number // empty')
+
+          if [ -n "$existing" ]; then
+            gh issue comment "$existing" --body \
+              "Still failing as of $(date -u +%Y-%m-%d). $RUN_URL"
+          else
+            gh issue create \
+              --title "Release dry-run is failing" \
+              --label "$LABEL" \
+              --body "$(printf '%s\n' \
+                "The weekly release dry-run failed: $RUN_URL" \
+                "" \
+                "This checks the release pipeline between releases — Play and App Store credentials, signing certs and provisioning profiles, and that a release build still validates against both stores. A failure here means the next release is likely to fail too, so it's worth fixing before cutting one." \
+                "" \
+                "Closing this issue is fine once the run is green; a later failure opens a new one.")"
+          fi
diff --git a/.github/workflows/store-release.yml b/.github/workflows/store-release.yml
index db4fe7ef..53365a9e 100644
--- a/.github/workflows/store-release.yml
+++ b/.github/workflows/store-release.yml
@@ -35,7 +35,7 @@ jobs:
       - name: Set up Ruby and Bundler
         uses: ruby/setup-ruby@v1
         with:
-          ruby-version: 3.2
+          ruby-version: 3.3
           bundler-cache: true
 
       # Setup Java so that we can build the appbundle.
@@ -94,7 +94,7 @@ jobs:
       - name: Set up Ruby and Bundler
         uses: ruby/setup-ruby@v1
         with:
-          ruby-version: 3.2
+          ruby-version: 3.3
           bundler-cache: true
 
       # Setup and cache Flutter to install packages and build.