From c6b6bef67da56f553e32bb83703228c792d297d4 Mon Sep 17 00:00:00 2001 From: Jasdeep Date: Tue, 3 Nov 2026 02:05:31 +0000 Subject: [PATCH] ci: pin the Supabase CLI the e2e job starts its stacks with latest resolved to CLI 3.0.0 on 2026-11-02, which rejects the [inbucket] section of the test stacks' config.toml, so every pull request's e2e job failed while starting Supabase. Pinned to 2.122.1, the last 2.x; moving to 3.x is its own change, with the config migrated. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/e2e.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/e2e.yml b/.github/workflows/e2e.yml index b256a2f..b7157dc 100644 --- a/.github/workflows/e2e.yml +++ b/.github/workflows/e2e.yml @@ -41,7 +41,11 @@ jobs: - name: Install Supabase CLI uses: supabase/setup-cli@v3 with: - version: latest + # Pinned: `latest` became CLI 3.0.0 on 2026-11-02, which refuses the + # [inbucket] section these stacks' config.toml still uses, and every + # pull request's e2e job failed before running a test. Move to 3.x + # deliberately, with the config migrated, rather than by surprise. + version: 2.122.1 # Raises the ghcr.io pull ceiling. Never fails the job: an anonymous pull # still works, it is only more likely to be throttled.