Repository navigation
feat: fall back to the GitHub release when npm cannot install the CLI - #457
Merged
Merged
Conversation
When npm fails to resolve, install or run a fixed CLI version, download the same version's GitHub release archive, verify it against the release checksums, and report the source through a new install-source output. Lockfile integrity mismatches still fail without falling back.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
avallete
approved these changes
Oct 30, 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
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.
v3 installs the CLI from npm only, so anything that stops npm producing a working binary fails the action outright. The case that prompted this was the 3.0.0-beta.16 release: the
supabasepackage became installable a few minutes before its platform binaries did, npm skipped the missing optional dependency, andsupabase --versionfailed withNo matching Supabase CLI binary package foundon macOS and Windows. A registry outage for a pinned version fails the same way.Now, when npm can't resolve, install or run a fixed version, the action logs a warning and installs that same version from its GitHub release instead:
npm viewresolved. A dist-tag that npm couldn't resolve still fails, since there's no reliable mapping frombeta/next/v2.stableto a release.checksums.txtand versioned archive names; older ones usesupabase_<version>_checksums.txtand unversioned names, and both are handled..apk, which carries the musl build, because the Linux tarball is glibc for v3.tar.exe, since Git Bash's GNU tar readsC:\...as a remote host.supabasebin still fails without falling back.There's a new
install-sourceoutput (npmorgithub-release), so a caller that specifically wants to test the npm package can flag a fallback. A new CI job forces the fallback on all three hosted runners, for both release naming schemes.The lockfile integrity check only covers the npm path. A fallback install is verified against the release's own checksums, not the lockfile.
🤖 Generated with Claude Code