fix: authenticate latest release lookup#430
Merged
Merged
Conversation
Coly010
approved these changes
May 20, 2026
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
2 participants
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.
Summary
github-tokeninput to authenticate the GitHub release lookup used byversion: latest.SUPABASE_CLI_GITHUB_TOKENand use it as a bearer token for the/repos/supabase/cli/releases/latestrequest.${{ github.token }}when testing or usinglatest.Root Cause
CI failed in
test (macos-latest, latest)because the action resolvedlatestthrough an unauthenticated GitHub REST API request and hit the low unauthenticated rate limit. The dependency bump in #429 was not the cause; the validate job passed and the failure happened inside the release lookup path.Impact
Pinned versions continue to work without a token. For
version: latest, callers can now pass${{ github.token }}to avoid unauthenticated API rate limiting while keeping the input optional for backward compatibility.Validation
bun run ci