Skip to content

fix(release): emit Homebrew postflight_steps instead of postflight - #97

Open
LiorAgnin wants to merge 1 commit into
xdevplatform:mainfrom
LiorAgnin:fix/homebrew-postflight-steps
Open

fix(release): emit Homebrew postflight_steps instead of postflight#97
LiorAgnin wants to merge 1 commit into
xdevplatform:mainfrom
LiorAgnin:fix/homebrew-postflight-steps

Conversation

@LiorAgnin

Copy link
Copy Markdown

Summary

Homebrew 7.0 deprecates the postflight stanza that GoReleaser 2.18 writes for hooks.post.install. Every brew command that loads xdevplatform/tap/xurl currently warns and asks users to report it to the tap.

Released GoReleaser cannot emit postflight_steps from hooks.post.install (goreleaser/goreleaser#6873). This drops the deprecated hook and writes postflight_steps through custom_block instead:

  • if OS.mac?on_macos
  • system_commandrun
  • #{staged_path} → Homebrew's install-time {{staged_path}} token, escaped as {{ "{{staged_path}}" }} so GoReleaser does not try to evaluate it

The generated cask keeps the same quarantine-attribute cleanup.

Once GoReleaser ships hooks.post.install_steps, this can move back to that option (and the stanza will sit in its canonical position after binary).

A matching tap PR updates the currently published cask so users stop seeing the warning before the next xurl release.

Homebrew 7.0 deprecates the `postflight` stanza that GoReleaser 2.18
writes for hooks.post.install, so every brew command against the tap
warns and asks users to file a bug.

hooks.post.install_steps is not in a released GoReleaser yet
(goreleaser/goreleaser#6873). Drop the deprecated hook and write
postflight_steps through custom_block, using Homebrew's declarative
run/on_macos DSL and an escaped {{staged_path}} token.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant