Homebrew: Cask Zap Rules and Cleanup Honesty
Homebrew tightened cask completeness and made cleanup failures visible. New casks must declare a zap stanza, with tooling to prefill it, while bundle cleanup now reports failures instead of exiting cleanly.
Duration: PT2M31S
Episode overview
This episode is a short developer briefing from Homebrew.
It explains recent repository work in plain language.
- Show: Homebrew
- Published: 2026-10-22T13:20:20Z
- Audio duration: PT2M31S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's October 22nd, 2026, this is Homebrew daily briefing.
The lead today is stricter accounting for leftover state, from cask uninstall files to failed removals being reported honestly instead of silently passing.
First, cask completeness. In PR 24315, new casks in official taps are now audited for a zap stanza on the operating system and architecture under test. The old no-zap comment couldn't be audited reliably, so contributors can now declare zap not required explicitly, serialized as an empty stanza so older Homebrew…
Second, more truthful cleanup. In PR 24289, brew bundle cleanup no longer prints misleading counts or exits zero when uninstall or untap steps fail. It reports per-item failures across extension managers, continues with remaining removals and cache cleanup, and exits non-zero even if later steps succeed. Completed…
In reliability fixes, PR 24325 signs temporary keg copies before restoring them to avoid path-specific Apple provenance failures, keeping the original file if signing the copy fails. Open work includes stripping high bytes before matched paths in keg relocation, and allowing Git downloads without global…
What's next: expect new cask…