Add Homebrew cask + auto-bump workflow#1
Merged
Conversation
- Casks/wechat-multi.rb: tappable cask pinned to v2.0.0 with the real release-asset sha256, livecheck against GitHub releases, ventura minimum, and a zap stanza covering clones/containers/prefs. - .github/workflows/cask.yml: on each published release, download the zip, recompute sha256, and bump the cask on main (also dispatchable). - build.yml: ignore Casks/** so cask bumps don't spin up the macOS build. - README (en + zh): document brew tap + install/upgrade/uninstall, drop Homebrew cask from the roadmap now that it exists.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements the Homebrew cask roadmap item so users can install WeChat Multi with
brewand get it kept up to date automatically.What's in here
Casks/wechat-multi.rb— a tappable cask:v2.0.0, with the real assetsha256(01bf16ae…, taken from the v2.0.0 release notes) — ships valid out of the box, not a placeholder.urlpoints at the standard release-download path (…/releases/download/v#{version}/WeChat-Multi-v#{version}.zip), matching the naming thereleaseworkflow already produces.livecheckvia:github_latest,depends_on macos: ">= :ventura"(matchesLSMinimumSystemVersion 13.0), and azap trash:stanza covering~/Applications/WeChat Multi, thecom.wechatmulti.clone*containers, and the prefs plist — mirroring the manual uninstall steps in the README.caveatsexplain the ad-hoc-signed first-launch right-click → Open, and the official-WeChat dependency..github/workflows/cask.yml— keeps the cask in lockstep with releases. The existingreleaseworkflow creates a draft release; when it's published (release: published), this job downloads the attached zip, recomputes the sha256, and commits the bump tomain. Alsoworkflow_dispatch-able with a tag input for manual re-syncs. Guards against non-vX.Y.Ztags and no-ops when the cask is already current.build.yml— addedCasks/**topaths-ignoreso the automated cask bumps don't trigger the macOS build.README (en + zh) — documented
brew tap+ install / upgrade / uninstall (--zap), and removed "Homebrew cask" from the roadmap now that it exists.How a user installs
Verification
This is a Linux CI container with no Swift/Xcode and no Homebrew, so I verified what I could here:
ruby -c Casks/wechat-multi.rb→ Syntax OKsedbump logic against the cask — bothversionandsha256lines rewrite correctlyNot verified here (no Homebrew available):
brew audit/brew install --caskagainst a live macOS machine, and an end-to-end run of the publish-triggered bump. Worth a manualbrew install --casksmoke test before merge.https://claude.ai/code/session_016iLRnVu9GdtixmXEHSVLD8
Generated by Claude Code