[jamesmontemagno]

Summary

• replace the deprecated postflight stanza with postflight_steps
• migrate the xattr invocation to Homebrew's structured run install-step DSL
• apply Homebrew's canonical stanza ordering and grouping
• declare the macOS dependency, use a platform-neutral description, and simplify the single-item zap

Validation

• ruby -c Casks/clicklight.rb
• brew style --cask aurorascharff/clicklight/clicklight
• brew audit --cask aurorascharff/clicklight/clicklight

[vercel]

@jamesmontemagno is attempting to deploy a commit to the Aurora Scharff's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Copilot review overview

🟢 Approval recommended

No unresolved review issues were identified.

Review tier: Lite
Findings: None

What changed in this PR

Updates the ClickLight Homebrew cask to use the current install-step DSL.

Changes:

• Replaces deprecated postflight with postflight_steps.
• Migrates xattr cleanup to structured run syntax.

File	Summary
Casks/​clicklight.rb	Migrates the post-install command to supported Homebrew syntax.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[vercel]

The postflight_steps block uses a non-existent run install step and an invalid template, breaking brew install --cask clicklight.

[jamesmontemagno]

postflight was deprecated see: https://brew.sh/2026/09/13/homebrew-7.0.0/

[vercel]

You're right that postflight is deprecated in Homebrew 7.0.0 (removal scheduled 2027-12-11) — but that doesn't make this migration valid. Two problems remain:

1. postflight_steps has no run step. The 7.0.0 notes are explicit that the *_steps DSL provides "structured file operations and configuration writes ... without arbitrary Ruby" — i.e. mkdir/touch/mv/ln_s/etc. with literal args, not command execution. run "/usr/bin/xattr", ... isn't a supported step, so evaluating the block raises NoMethodError and brew install --cask clicklight fails outright.
2. {{appdir}} isn't a valid template in the steps DSL (the original used Ruby interpolation #{appdir}).

The key point: clearing the quarantine attribute (xattr -cr) is command execution, which the steps DSL cannot express at all — so there's no postflight_steps equivalent for this cask.

Net effect: deprecated postflight still works until Dec 2027, whereas the current code is broken today. Recommended paths: keep the (deprecated but functional) postflight block for now, or drop the xattr step entirely if the notarized download doesn't actually need de-quarantining. It just can't be moved into postflight_steps as written.

[jamesmontemagno]

This is supported in Homebrew 7.0.0. I verified against the 7.0.0 tag itself:

• Homebrew::InstallSteps::DSL#run is defined in Library/Homebrew/install_steps.rb (line 715).
• appdir is listed in ABSOLUTE_TEMPLATE_TOKENS (line 65) and CONTENT_PATH_TOKENS (line 906).
• Serialized run arguments are expanded via expand_template_tokens (line 1246).
• Homebrew's own 7.0.0 tests execute run "/usr/bin/true" inside postflight_steps.

I also evaluated this exact DSL locally on Homebrew 7, which serializes successfully as a run step, and ran brew style, brew audit, and brew install --cask --dry-run; all pass. The constrained run action is not arbitrary Ruby, and {{appdir}} is the documented deferred template form, so no code change is needed.

Note

Auto-replied by the GitHub Copilot app.

[vercel]

You're right, and I was wrong — thanks for the precise pointers. I verified against the 7.0.0 tag directly:

• Homebrew::InstallSteps::DSL#run(command, args: [], …) is defined at Library/Homebrew/install_steps.rb:715 and serializes as a "run" step, executed by run_serialised_command (line 1244) via @command.run(...).
• appdir is in both ABSOLUTE_TEMPLATE_TOKENS (line 65) and CONTENT_PATH_TOKENS (line 906), and {{appdir}} is expanded through expand_template_tokens (line 1246).

My earlier analysis was based on the initial cask-install-steps PR (#22373), which predated the run step landing — it wasn't in that iteration, so I incorrectly concluded no command execution was possible. The shipped 7.0.0 added it. Your migration is valid; dismissing the suggestion. 🙏

[sklakegg]

Great tool @aurorascharff ⭐

Any chance we can have this merged so we can get rid of warnings when using brew? 🙏

[aurorascharff]

thanks for the nudge! @sklakegg yep!