docs: document brew trust step for Homebrew 6.0+#164
Open
eboudrant wants to merge 1 commit into
Open
Conversation
Homebrew 6.0 (June 2026) requires third-party taps to be trusted before it will load their casks, so install/upgrade now fails with "Refusing to load cask ... from untrusted tap". Add the one-time `brew trust eboudrant/tap` step to the README, the docs site, and the in-app update banner command. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
Homebrew 6.0 (June 2026) requires third-party taps to be trusted before it will load their casks. Install and upgrade now fail with:
This documents the one-time
brew trust eboudrant/tapstep in three places:brew trustwhen the upgrade hits the error.<pre>block with a caption explaining the 6.0+ requirement.brew trust eboudrant/tap &&into the in-app update banner's copy command.brew trustis idempotent, so it stays a no-op once trusted.Test plan
home.jschange only affects the update banner's command string. The banner renders only whenupdateCheck.checkForUpdate()returnsavailable: true, which requiresPAPASTUD_VERSIONto be set (src/updateCheck.js:75). The Playwright test server doesn't set it, so the banner never renders under test and no screenshot baseline changes. Docker screenshot run was blocked locally by a Docker Desktop corp sign-in; relying on CI's Screenshot Tests to confirm.