📝 Fix The Homebrew Install Command - #93
Merged
Merged
Conversation
dunningdan
changed the title
dunningdan
force-pushed
the
docs/brew-trust-install-step
branch
from
August 5, 2026 20:03
68fe9e5 to
72fe5cb
Compare
dunningdan
changed the title
dunningdan
force-pushed
the
docs/brew-trust-install-step
branch
from
August 5, 2026 20:07
72fe5cb to
5039641
Compare
The documented install fails on a clean machine:
$ brew tap pixee/pixee
==> Tapping pixee/pixee
Cloning into '/opt/homebrew/Library/Taps/pixee/homebrew-pixee'...
$ brew install pixee
Error: Refusing to load formula pixee/pixee/pixee from untrusted tap pixee/pixee.
Two causes. `pixee/homebrew-pixee` was renamed to `pixee/homebrew-tap`, so the
documented tap name resolves through a GitHub redirect and installs a second tap
for the same repo, after which the short name is ambiguous. And since Homebrew
6.0.0 a non-official tap must be trusted before Homebrew will load a formula from
it by short name.
`brew install pixee/tap/pixee` fixes both: correct tap, and installing by fully
qualified name trusts that one formula, so no `brew trust` step is needed. Verified
from a clean state twice, once confirming the old instructions install nothing and
once confirming this one yields pixee 0.17.0 from a single tap.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014z9k8q5CwGagYfi5CLgYr9
dunningdan
force-pushed
the
docs/brew-trust-install-step
branch
from
August 5, 2026 20:08
5039641 to
b11bd4b
Compare
|
dunningdan
marked this pull request as ready for review
August 5, 2026 20:22
gilday
approved these changes
Aug 5, 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.
The documented Homebrew install installs nothing. From a clean machine:
Step one succeeds and gives no hint of a problem, so this surfaces at step two as what looks like a security error rather than a stale instruction.
Two causes:
pixee/homebrew-pixeewas renamed topixee/homebrew-tap, sopixee/pixeeresolves through a GitHub redirect and installs a second tap for the same repo. With both present the short name is ambiguous:Error: Formulae found in multiple taps.brew install pixee/tap/pixeefixes both. Correct tap, and installing by fully qualified name trusts that one formula, so nobrew truststep is needed:Both paths were run from a fully reset state (no binary, no taps, empty trust file) rather than reasoned about: the old instructions install nothing, the new one yields
pixee 0.17.0from a single tap.The trust mechanics are deliberately not explained in the README. A reader installing the CLI does not need Homebrew's trust model, only a command that works, and Homebrew's own error message points anyone who needs it at
brew trust.The customer-facing copy in pixee/docs
docs/api/cli.mdhas the same two-line block and the same bug. That page is already being rewritten in pixee/docs#295, so it belongs there.