ci: pin the Supabase CLI instead of resolving "latest" - #6
Merged
Merged
Conversation
The control plane e2e failed on main with "Failed to resolve latest Supabase CLI release: rate limit exceeded". Nothing in the repo caused it: supabase/setup-cli resolves "latest" through an unauthenticated call to the GitHub releases API, which is rate limited per runner IP, and today's run of PRs used the budget up. The action's source confirms the API is only consulted to resolve "latest", so an explicit version skips the call entirely. Pinning also buys determinism. On "latest" a new Supabase CLI release can turn CI red with no commit to point at, which is a bad way to spend a morning.
dabelle
pushed a commit
that referenced
this pull request
Sep 19, 2026
ci: pin the Supabase CLI instead of resolving "latest"
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.
The control plane e2e failed on
mainwith:Nothing in the repo caused it.
supabase/setup-cliresolveslatestthrough an unauthenticated call to the GitHub releases API, which is rate limited per runner IP, and today's run of PRs used the budget up. The action's source confirms that API is consulted only to resolvelatest, so an explicit version skips the call.Pinning also buys determinism: on
latest, a new Supabase CLI release can turn CI red with no commit to point at.This PR is also the check that the fix works, since it exercises the same job that failed.