Skip to content

ci: pin supabase CLI to 2.98.2 (v2.99.0 broke asset naming) #2286

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
riderx merged 1 commit into from
May 18, 2026
Merged

ci: pin supabase CLI to 2.98.2 (v2.99.0 broke asset naming) #2286

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
8 changes: 7 additions & 1 deletion .github/workflows/build_and_deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,14 @@ jobs:
run: bun install
- name: Install Supabase CLI
uses: supabase/setup-cli@v2.0.0
# Pinned to 2.98.2 because Supabase CLI v2.99.0 (2026-05-18) ships
# release assets with version in the filename (supabase_2.99.0_linux_amd64.tar.gz)
# while setup-cli@v2.0.0 hardcodes the unversioned name
# (supabase_linux_amd64.tar.gz) for any version >= 1.28.0, causing 404.
# Revert to `latest` once setup-cli ships a fix or Supabase restores
# the unversioned assets. Tracking: https://github.com/supabase/setup-cli
with:
version: latest
version: 2.98.2
- name: Show Supabase CLI version
run: supabase --version
- name: Prepare Supabase
Expand Down
Loading