Skip to content

ci: pin the Supabase CLI instead of resolving "latest" #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dabelle merged 1 commit into from
Sep 17, 2026
Merged

ci: pin the Supabase CLI instead of resolving "latest" #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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: |
Expand Down
Loading