🧰 chore: fix Brewfile drift surfaced by the new brew bundle script - #14
Merged
Conversation
brew bundle surfaced both: spark was renamed upstream, and newer Homebrew refuses the grishka/grishka tap until a one-time `brew trust grishka/grishka` — documented on the cask line so fresh machines know why the fetch fails. Co-Authored-By: Claude Fable 5 <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
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.
The Phase 2 run_onchange script's first real run caught two stale Brewfile entries: the upstream
spark→spark-appcask rename, andneardrop's tap now requiring a one-timebrew trust grishka/grishkaunder newer Homebrew (documented on the cask line).🤖 Generated with Claude Code