From 295540cbd596392a175cf773d738de320a18bd8f Mon Sep 17 00:00:00 2001 From: HamChowderr Date: Wed, 17 Jun 2026 19:13:02 -0700 Subject: [PATCH] ci: pin Supabase CLI to 2.107.0 in db-types job MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 'db types fresh' job used `version: latest` on supabase/setup-cli, which resolves the newest release via an unauthenticated GitHub API call. That got rate-limited on a shared runner ("Failed to resolve latest Supabase CLI release: rate limit exceeded") and failed the job in ~9s with no real type drift. Pinning downloads the release asset directly — deterministic and immune to that anonymous rate limit. Bump deliberately when a migration needs a newer CLI. Closes foreman-fjl3. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/test.yml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 5194d6b6..ba78d1f9 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -92,7 +92,12 @@ jobs: cache: npm - uses: supabase/setup-cli@v1 with: - version: latest + # Pinned (not `latest`) so the action downloads a fixed release asset + # instead of making an unauthenticated GitHub API call to resolve the + # newest version — that call is rate-limited on shared runners and + # flaked this job ("Failed to resolve latest Supabase CLI release: + # rate limit exceeded", foreman-fjl3). Bump deliberately when needed. + version: 2.107.0 - run: npm ci - name: Start local Supabase run: npx supabase start