fix: prefer gh auth over SHPIT_GH_TOKEN for installs#5
Merged
anand-testcompare merged 1 commit intoApr 21, 2026
Merged
Conversation
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.
Summary
gh auth token, and only then trySHPIT_GH_TOKENtabex,osyrra, andmeshix-cliWhy
A local shell can already have
SHPIT_GH_TOKENexported for automation work. When that token does not have the same release access as the logged-inghaccount, installs can fail with a GitHub 404 even thoughgh auth loginis correct. This change makes the normal local install path prefer the localghsession instead of the automation fallback token.Validation
./scripts/validate-formulae.sh