Skip to content

docs(packaging): explain what keeps the core cask variant apart #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kipavy merged 1 commit into from
Aug 24, 2026
Merged

docs(packaging): explain what keeps the core cask variant apart #178

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions packaging/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,6 +177,11 @@ Developer account. `brew style` and the rest of the audit are clean, so this is
the only thing standing in the way.

`scripts/gen-homebrew-cask.sh <tag> --core` emits the variant for that PR, kept
ready for the day notarization exists: core rejects casks whose caveats tell the
user to reinstall with `--no-quarantine`, so that hint is dropped, leaving the
right-click-Open instructions.
ready for the day notarization exists: core is hostile to caveats that talk the
user out of Gatekeeper, so the quarantine-clearing `xattr` command the tap
caveat carries is dropped there, leaving the right-click-Open instructions.

Never put `brew install --no-quarantine` in either variant. Homebrew 6 removed
the flag, so the hint fails with `Error: invalid option: --no-quarantine` for
tap users, and core rejected it before that. `brew audit` does not catch it, so
the `cask-audit` action greps the generated cask and fails the run (#176).
Loading