Skip to content

docs: use the fully-qualified brew install name, not the bare one - #13

Merged
samyakLambda merged 1 commit into
mainfrom
docs/brew-install-fully-qualified-name
Aug 18, 2026
Merged

docs: use the fully-qualified brew install name, not the bare one#13
samyakLambda merged 1 commit into
mainfrom
docs/brew-install-fully-qualified-name

Conversation

@samyakLambda

Copy link
Copy Markdown
Contributor

Reported live by a user following these exact instructions verbatim:

Error: Refusing to load formula lambdatest/rook/rook from untrusted tap lambdatest/rook.

Root cause

Homebrew requires third-party-tap formulae to be trusted before loading
(default-on since a recent Homebrew version, trust.rb) — except when
installed by the fully-qualified user/tap/formula name, which Homebrew's
own explicitly_allowed? check treats as sufficient explicit consent
(confirmed directly in Homebrew's source: it checks whether the qualified
name appears literally in the invoking command's own args).

brew-smoke.yml has always installed by the fully-qualified name
(brew install lambdatest/rook/rook) — exactly why CI never caught this.
The README documented the bare form (brew install rook, after a separate
brew tap), which doesn't satisfy that check. CHANGELOG.md already had
the correct fully-qualified form.

Verified live

  • brew tap LambdaTest/rook ... then brew install rook on a fresh tap:
    reproduces the exact reported error.
  • brew tap LambdaTest/rook ... then brew install lambdatest/rook/rook
    on the same tap: succeeds, no trust prompt.

Agent-authored: Claude Sonnet 5, Claude Code CLI.

The documented Homebrew flow (`brew tap ...` then `brew install rook`)
hits Homebrew's tap-trust gate: `Error: Refusing to load formula
lambdatest/rook/rook from untrusted tap lambdatest/rook.` Reported live
by a user following these exact instructions verbatim; reproduced
byte-for-byte on a fresh tap.

Root cause: Homebrew requires third-party-tap formulae to be trusted
before loading (default-on, `trust.rb`), except when installed by the
fully-qualified `user/tap/formula` name, which its own
`explicitly_allowed?` check treats as sufficient explicit consent —
confirmed directly in Homebrew's source. brew-smoke.yml has always
installed by the fully-qualified name (`brew install
lambdatest/rook/rook`), which is exactly why CI never caught this —
only the README's bare `brew install rook` form is affected.
CHANGELOG.md already had the correct form.

Verified live: `brew install rook` after the tap fails with the exact
reported error; `brew install lambdatest/rook/rook` on the same tap
succeeds with no trust prompt at all.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@samyakLambda
samyakLambda merged commit 68cfa1a into main Aug 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant