Skip to content

fix(brew): support cask command wrappers and run steps #11472

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
jdx merged 3 commits into from
Jul 29, 2026
Merged

fix(brew): support cask command wrappers and run steps #11472

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ff0d21b
fix(brew): support cask command wrappers and run steps
jdx Jul 29, 2026
242adf0
fix(brew): preserve command wrapper semantics
jdx Jul 29, 2026
232f5d8
fix(brew): harden cask lifecycle metadata
jdx Jul 29, 2026
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
27 changes: 15 additions & 12 deletions docs/bootstrap/packages/brew.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,24 +67,27 @@ installs app bundles into `/Applications` while recording the version under
"brew-cask:homebrew/cask/visual-studio-code" = "latest"
```

`brew-cask` currently supports app-bundle casks (`app` artifacts), binary casks
(`binary` artifacts), simple macOS installer packages (`pkg` artifacts), and
shell completions (`bash_completion`, `fish_completion`, `zsh_completion`, and
`brew-cask` currently supports app-bundle casks (`app` artifacts), binary and
generated command-wrapper casks (`binary` and `command_wrapper` artifacts),
simple macOS installer packages (`pkg` artifacts), and shell completions
(`bash_completion`, `fish_completion`, `zsh_completion`, and
`generate_completions_from_executable`) from dmg and common archive formats.
Binary artifacts are staged in the Caskroom
and linked into the Homebrew prefix, usually under `<prefix>/bin`. Package
installers run through mise's normal system-package sudo path, so non-interactive
runs never hang waiting for a password. Pkg casks must include `pkgutil` receipt
IDs in their `uninstall` metadata so mise can verify installed state after the
Binary artifacts and generated wrappers are staged in the Caskroom and linked
into the Homebrew prefix, usually under `<prefix>/bin`. Package installers run
through mise's normal system-package sudo path, so non-interactive runs never
hang waiting for a password. Pkg casks must include `pkgutil` receipt IDs in
their `uninstall` metadata so mise can verify installed state after the
installer writes files outside the Caskroom. `zap` `pkgutil` IDs are treated as
cleanup metadata, not install receipts. For casks with lifecycle hooks, mise
fetches the sha256-verified cask Ruby source pinned by the API metadata and runs
supported `preflight`/`postflight` hooks through its own Cask DSL shim, without
delegating to Homebrew. mise also supports structured `preflight_steps` and
`postflight_steps` for `move`/`remove` operations against `staged_path`. Casks
that require custom installer choices, services, unsupported hook DSL, unsupported
structured lifecycle steps, or other cask artifact types fail with a clear
unsupported artifact error instead of delegating to Homebrew.
`postflight_steps` for `move`/`remove` operations against `staged_path` and
`run` operations using Homebrew's serialized command bases, arguments,
environment, guards, and sudo setting. Casks that require custom installer
choices, services, unsupported hook DSL, unsupported structured lifecycle
steps, or other cask artifact types fail with a clear unsupported artifact
error instead of delegating to Homebrew.

This exists because shared-library packages — postgres, ffmpeg, imagemagick,
php — fundamentally can't be served by mise's per-project backends like
Expand Down
Loading