vibeproxy 1.8.129 (new cask)#257601
Merged
bevanjkay merged 3 commits intoHomebrew:mainfrom Apr 5, 2026
Merged
Conversation
bevanjkay
reviewed
Apr 4, 2026
Co-authored-by: Bevan Kay <bevanjkay@gmail.com>
bevanjkay
approved these changes
Apr 5, 2026
Member
|
Adding a tag to merge this, then @BrewTestBot can bump the next version in time. |
Member
|
Thank you @fettpl |
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
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.
Summary
Adds a new official cask for VibeProxy.
Verification
brew audit --cask --online vibeproxyis error-free.brew style --fix vibeproxyreports no offenses.brew audit --cask --new vibeproxyworked successfully.HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask vibeproxyworked successfully.brew uninstall --cask vibeproxyworked successfully.Notes
arm64only. Upstream currently publishes Intel artifacts as untested while other install docs still say Intel is unsupported.auto_updates trueis included because the app uses Sparkle for in-app updates.zapis intentionally limited to~/Library/Preferences/com.vibeproxy.app.plist. The app also uses~/.cli-proxy-api, but that appears to hold user-owned shared auth/config state and is intentionally not removed byzap.v1.8.129is sourced from the signed and notarizedVibeProxy-arm64.dmg. The matchingVibeProxy-arm64.zipstill fails local signature verification after extraction, so the cask intentionally targets the DMG artifact instead.AI Disclosure
AI helped draft the cask and PR copy. The token, release URL, SHA256, architecture scope, Sparkle auto-update behavior, and
zappath were manually verified. Homebrew style, audit, and token-based install/uninstall checks were run locally.