From 2c286eb29b2e10542923c11e442a18a14d34cc4d Mon Sep 17 00:00:00 2001 From: Danial Beg Date: Mon, 2 Nov 2026 12:45:46 -0800 Subject: [PATCH] Fix edge function deploy under Supabase CLI v3 The deploy job installed the CLI at `latest`, which became v3.0.0 on 2026-11-02. v3 asks before any change to a hosted project and fails when nothing can answer, so the deploy on main stopped at the prompt and changed nothing. Pin the CLI to 3.0.0 so a new major can't break deploys unannounced, pass --yes, and use --remote in place of the deprecated --project-ref. --- .github/workflows/ci.yml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 688bca3..8c30ca7 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -84,9 +84,11 @@ jobs: steps: - uses: actions/checkout@v4 + # Pinned: `latest` picked up CLI v3 on the day it shipped, and its new + # confirmation prompt failed this deploy. Bump it on purpose. - uses: supabase/setup-cli@v1 with: - version: latest + version: 3.0.0 # Deploys every function under supabase/functions, reading verify_jwt # from supabase/config.toml. Functions deployed to the project but absent @@ -97,7 +99,11 @@ jobs: # somebody remembered to push them by hand, and the digest spent weeks # running against code nobody had deployed. A red build is the cheapest # version of finding that out. + # + # --yes: v3 asks before any change to a hosted project and fails when + # nothing can answer, as in CI. --remote replaces the deprecated + # --project-ref. - name: Deploy env: SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }} - run: supabase functions deploy --project-ref oybmtfnarflrceukvays + run: supabase functions deploy --remote=oybmtfnarflrceukvays --yes