ci: pin Supabase CLI to 2.107.0 in db-types job - #19
Merged
Conversation
The 'db types fresh' job used `version: latest` on supabase/setup-cli, which
resolves the newest release via an unauthenticated GitHub API call. That got
rate-limited on a shared runner ("Failed to resolve latest Supabase CLI
release: rate limit exceeded") and failed the job in ~9s with no real type
drift. Pinning downloads the release asset directly — deterministic and
immune to that anonymous rate limit. Bump deliberately when a migration needs
a newer CLI.
Closes foreman-fjl3.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
db types freshjob pinssupabase/setup-cli@v1toversion: latest, which resolves the newest release via an unauthenticated GitHub API call. On shared runners that call is rate-limited, and it flaked on PR #18:The job died in ~9s — before doing any real work — with no actual type drift. A blind re-run cleared it, but it can recur any time.
Fix
Pin the CLI to a fixed version (
2.107.0— current stable, and exactly what the passing re-run installed). With an explicit version the action downloads the release asset directly, so there's no "resolve latest" API call to rate-limit. Deterministic and immune to the anonymous limit; bump deliberately when a migration needs a newer CLI.Verification
This PR's own
db types freshrun exercises the change end-to-end.Refs foreman-fjl3.
🤖 Generated with Claude Code