Activity

1. riderx commented on Mar 19, 2026

   

   riderx

   on Mar 19, 2026

   Contributor

   More actions

   made PR for it #400

   🎉React with 🎉1Reacted by Ben Standefer
2. aguynamedben commented on Apr 1, 2026

   

   aguynamedben

   on Apr 1, 2026

   More actions

   There's a PR for it, the PR was merged, however there are failing lints on master now, and there has been no release since the merge to master, so it's not really usable short of pinning a sha1 in your GitHub Action.
3. jgoux commented on Apr 3, 2026

   

   jgoux

   on Apr 3, 2026

   Last edited by jgoux

   Contributor

   More actions

   Hey all, thanks for the ping. I gave this Github Action some love today.

   Could you try the upcoming version 2 commit and tell me if it works for you?

     - uses: supabase/setup-cli@2eca1b4d35d9016e560c763c9159a350aa80c370

   Here is the changelog :

   v2.0.0

   This release modernizes supabase/setup-cli and makes the default version
   selection much smarter.

   Breaking changes

   Omitted version no longer uses a pinned default first

   If you omit with.version, the action now tries to detect the Supabase CLI
   version from the repository root lockfile:

   1. bun.lock
   2. pnpm-lock.yaml
   3. package-lock.json

   If no supported lockfile is found, it falls back to latest.

   This means the default behavior now follows the CLI version already declared by
   your repository when possible.

   Before:

   steps:
     - uses: supabase/setup-cli@v1

   Now:

   steps:
     - uses: supabase/setup-cli@v2

   If your root lockfile already pins supabase, that version is used
   automatically.

   If you want to keep full control, explicit versions still win:

   steps:
     - uses: supabase/setup-cli@v2
       with:
         version: 2.84.2

   And latest remains available when you want a moving target:

   steps:
     - uses: supabase/setup-cli@v2
       with:
         version: latest

   Improvements

   Simpler Bun-based action runtime

   setup-cli@v2 now runs as a Bun-based composite action. The public interface is
   still the same, but the implementation is simpler and the repository no longer
   ships checked-in build artifacts.

   Usage stays straightforward:

   steps:
     - uses: supabase/setup-cli@v2

   Better examples for local Supabase workflows

   The docs now include clearer examples for common GitHub Actions flows, including
   running the local Supabase stack and exporting environment variables for app
   tests.

   Example:

   steps:
     - uses: supabase/setup-cli@v2
     - run: supabase init
     - run: supabase start
     - name: Export local Supabase env vars
       run: |
         supabase status -o env \
           --override-name api.url=SUPABASE_URL \
           --override-name auth.service_role_key=SUPABASE_SERVICE_ROLE_KEY \
           >> .env.test
     - run: bun test

   Notes

   • supabase/setup-cli@v2 still supports ubuntu-latest, macos-latest, and
     windows-latest.
   • If you rely on self-hosted runners, make sure the runner has the shell and
     network access needed to bootstrap the composite action and download the
     Supabase CLI.

   👍React with 👍2Reacted by Erdenetugs and Trevor Hartman
4. devth commented on Apr 16, 2026

   

   devth

   on Apr 16, 2026

   More actions

   README on main branch shows:

   steps:
     - uses: supabase/setup-cli@v2
   

   This will result in:

   Unable to resolve action `supabase/setup-cli@v2`, unable to find version `v2`
   

   👍React with 👍7Reacted by Martin DONADIEU, Vlad Kolbaia, NorthBei, Vick Khera, adeshchopade, Raymond Berglind and James Hunt
5. jgoux commented on Apr 21, 2026

   

   jgoux

   on Apr 21, 2026

   Contributor

   More actions

   It should be good now, sorry about that!
6. jgoux

   closed this as completedon Apr 21, 2026
7. devth commented on Apr 21, 2026

   

   devth

   on Apr 21, 2026

   More actions

   @jgoux awesome thanks!

   🎉React with 🎉1Reacted by Vick Khera
8. emjayess commented on Jun 12, 2026

   

   emjayess

   on Jun 12, 2026

   More actions

   All of supabase.com's documentation still only specifies supabase/setup-cli@v1

   which is problematic out of the gate now.