fix: the brew instructions we shipped stop on a clean machine (v1.44 W6 follow-up) - #390
Merged
Merged
Conversation
…W6 follow-up) The tap is live at cli-pulse/homebrew-tap, and publishing it turned up a step neither the cask nor the release notes accounted for. Homebrew 6 refuses to load casks from any third-party tap until it is trusted: Error: Refusing to load cask cli-pulse/tap/cli-pulse from untrusted tap. So the two-command instructions I wrote into the release notes — tap, then install — stop with an error on every machine that isn't mine. Found by actually running the install path from a clean untap rather than assuming it worked because `brew audit` passed; audit operates on a tap you already have. Now documented in the release notes, in the tap's README, and in the post-release checklist that `update_cask.sh` prints, which also gained the copy-into-tap-and-push commands it was previously hand-waving at as "Owner-gated". Verified end to end after publishing: brew untap → brew tap → brew trust → brew info resolves 1.43.0 brew fetch --cask cli-pulse downloads + checksum OK `fetch` rather than `install` on purpose — this machine has a working CLI Pulse.app in /Applications and overwriting a developer's own build to prove a checksum is a bad trade. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Jul 28, 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
1 participant
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.
What publishing the tap turned up
The tap is live at
cli-pulse/homebrew-tap. Publishing it exposed a step neither the cask nor the release notes accounted for.Homebrew 6 refuses to load casks from any third-party tap until it is trusted:
So the two-command instructions in the release notes — tap, then install — stop with an error on every machine that isn't mine.
Found by running the install path from a clean
brew untap, not by assuming it worked becausebrew auditpassed. Audit operates on a tap you already have locally, so it cannot see this at all.Fixed in three places
github-release.sh)update_cask.shprints — which also gained the actual copy-into-tap-and-push commands it was previously hand-waving at as "Owner-gated"Verified end to end after publishing
brew untap→brew tap→brew trust→brew info --cask cli-pulsebrew fetch --cask cli-pulsefetchrather thaninstalldeliberately: this machine has a workingCLI Pulse.appin/Applications, and overwriting a developer's own build to prove a checksum is a bad trade.🤖 Generated with Claude Code