Skip to content

fix(release): generate a cask Homebrew 7 accepts - #388

Merged
AdamXweb merged 1 commit into
mainfrom
fix/homebrew-cask-verified
Oct 8, 2026
Merged

AdamXweb merged 1 commit into
mainfrom
fix/homebrew-cask-verified

Conversation

@adamXbot

@adamXbot adamXbot commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

What and why

Homebrew 7 warns on every install and upgrade of the cask:

Warning: Calling the verified parameter in the url stanza is deprecated! Use the default URL verification behaviour instead.

verified: comes from the template in homebrew-release.yml, so fixing only the tap would bring it back with the next release. The tap's live cask is fixed in privacykey/homebrew-tap#23.

While checking the template against Homebrew 7.0.8, I found a worse problem. The cask this workflow would write for v0.3.0 does not load at all:

Warning: Calling string comparison format for `depends_on macos:` is deprecated! There is no replacement.
Cask 'privacytracker' definition is invalid: invalid 'depends_on macos' value: unknown or unsupported macOS version: "13.5"

Homebrew 7 accepts only a release name there. Once the v0.3.0 bump PR merged in the tap, brew install --cask privacytracker would have failed for everyone.

  • The url drops verified:. The url and homepage share a host, and Homebrew 7 ignores the parameter anyway.
  • The release context maps the major of tauri.conf.json's minimumSystemVersion to Homebrew's release name, using Homebrew 7's own MacOSVersion::RELEASES table. 13.5 becomes :ventura, which Homebrew reads as 13.0 or later. Homebrew can't express a point release, and the app's own LSMinimumSystemVersion still refuses 13.0 to 13.4 at launch. An unknown major stops the job with an error instead of guessing.

How it was verified

All checks used Homebrew 7.0.8 on macOS, loading each cask with Cask::CaskLoader::FromPathLoader through brew ruby. Homebrew 7's brew style refuses a cask outside a tap.

  • Control: the tap's current cask reproduces the exact warning.
  • Tap cask without verified:: loads with no warning; the url specs are identical ({user_agent: :default}).
  • Template output: rendered with VERSION=0.3.0 and MINIMUM_MACOS=13.5, it loads with no warning and depends_on macos: :ventura. Before this change the same render raised the error above.
  • The case block, run on its own: 13.5 gives ventura, 26.0 gives tahoe, and 16.0 exits 1 with ::error::.
  • actionlint on the workflow: clean.
  • Not run end to end: it fires only when a release is published.

No CHANGELOG entry. The warning goes away for users through the tap PR, and this change only stops the next release from bringing it back or shipping an unloadable cask.

Checklist

  • One coherent change: the generated cask loads under Homebrew 7
  • No user-facing strings, UI or dependency changes

🤖 Generated with Claude Code

Two stanzas in the homebrew-release template no longer suit Homebrew 7:

- `verified:` on the url is accepted only as a no-op and prints a
  deprecation warning on every install and upgrade.
- `depends_on macos: ">= 13.5"` fails to load: Homebrew 7 takes only a
  release name there ("unknown or unsupported macOS version"). The cask
  this workflow writes for v0.3.0 would have broken `brew install` for
  everyone once the tap PR merged.

The url drops `verified:`, and the release context maps the major of
tauri.conf.json's minimumSystemVersion to Homebrew's release name (13.5
becomes :ventura, which Homebrew reads as 13.0 or later; the app's own
LSMinimumSystemVersion still refuses 13.0-13.4). An unknown major stops
the job instead of guessing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@adamXbot
adamXbot requested a review from AdamXweb as a code owner October 8, 2026 10:01
@AdamXweb
AdamXweb merged commit 32cb694 into main Oct 8, 2026
18 of 20 checks passed
@AdamXweb
AdamXweb deleted the fix/homebrew-cask-verified branch October 8, 2026 12:16
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.

2 participants