From 4ea261c181208f0567465fba78854ece0684562f Mon Sep 17 00:00:00 2001 From: thetechnologist1911 Date: Thu, 17 Sep 2026 19:13:50 -0400 Subject: [PATCH] ci: pin the Supabase CLI instead of resolving "latest" The control plane e2e failed on main with "Failed to resolve latest Supabase CLI release: rate limit exceeded". Nothing in the repo caused it: supabase/setup-cli resolves "latest" through an unauthenticated call to the GitHub releases API, which is rate limited per runner IP, and today's run of PRs used the budget up. The action's source confirms the API is only consulted to resolve "latest", so an explicit version skips the call entirely. Pinning also buys determinism. On "latest" a new Supabase CLI release can turn CI red with no commit to point at, which is a bad way to spend a morning. --- .github/workflows/ci.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 1eb3a79..ffb289f 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -84,7 +84,11 @@ jobs: - uses: supabase/setup-cli@v2 with: - version: latest + # Pinned, not "latest". Resolving "latest" costs an unauthenticated + # GitHub API call that is rate limited per runner IP, and it failed + # exactly that way on a busy day. Pinning also stops a new CLI + # release from breaking CI with no commit to blame. + version: 2.117.0 - name: Install restic run: |