Repository navigation
fix(release): generate postflight_steps in the homebrew cask - #177
isaacsokari wants to merge 1 commit into
Conversation
Homebrew deprecated the cask `postflight` block, so `brew update` warns about runware.rb. Move the quarantine hook to `install_steps`, which GoReleaser v2.19+ renders as the declarative `postflight_steps` stanza.
|
Important Review skippedAuto reviews are disabled on this repository. To trigger a review, include
|
postflight Warning
Description
Homebrew deprecated the cask
postflightblock, sobrew updatenow warnsCalling postflight is deprecated! Use postflight_steps instead.and points at ourrunware.rb.This PR moves the quarantine hook to GoReleaser's
install_steps(v2.19+; CI's~> v2resolves to v2.20.0), which renders the declarativepostflight_stepsstanza. The warning clears once the next release regenerates the tap's cask.Checked locally against Homebrew: the rendered cask loads without the warning, passes
brew style, and its step stripscom.apple.quarantinefrom a staged binary.Changes made
hooks.post.installRuby block withhooks.post.install_stepsin the goreleaser config, so the cask emitspostflight_stepsinstead ofpostflight.on_macos+runwith{{ .StagedPath }}), keeping the samexattr -drbehaviour and fail-on-error semantics.