macOS: Homebrew cask disabled for failing Gatekeeper, README install command no longer gets updates #2817

Bug Report

Homebrew disabled the pyfa cask on 2026-09-01 because it fails the macOS Gatekeeper check, so the install command in the README no longer gets you current releases. I know the README lists Homebrew as a third-party package, so I'm reporting this mainly so the instructions can be updated and Mac users know why they've stopped getting updates.

Expected behavior:

brew upgrade --cask pyfa updates pyfa to the latest release, as the README's Homebrew section suggests.

Actual behavior:

Homebrew refuses to upgrade and stays on 2.68.0, while the latest release is 2.69.3:

Warning: Not upgrading pyfa, it is disabled because it does not pass the macOS Gatekeeper check! It was disabled on 2026-09-01.
==> 1 Deprecated or disabled package
pyfa (disabled)

brew bundle is easy to miss this with, because it only prints Using pyfa.

Detailed steps to reproduce:

1. Have the pyfa cask installed through Homebrew.
2. Run brew upgrade --cask pyfa.
3. See the warning above.

Fits involved in EFT format (Edit > To Clipboard > EFT):

N/A, this isn't related to a fit.

Release or development git branch? Please note the release version or commit hash:

Installed: release 2.68.0, from the Homebrew cask. Latest release at the time of writing: 2.69.3.

Operating system and version (eg: Windows 10, OS X 10.9, OS X 10.11, Ubuntu 16.10):

macOS 27.0.1 (arm64)

Other relevant information:

• The cask definition has disable! date: "2026-09-01", because: :fails_gatekeeper_check.
• The installed 2.68.0 app has an ad-hoc signature (codesign reports Signature=adhoc), and spctl -a -vv reports rejected. I haven't checked the 2.69.3 builds.
• The cask's download URL also uses the old pyfa-v#{version}-mac.zip name. Recent releases publish -mac-arm64.zip and -mac-x86_64.zip, so reviving the cask would need that changed too.
• I didn't find an existing issue for this. Dependency update: macOS release tracking issue #2548 discusses macOS signing and quarantine in passing, and Provide DMG with universal/apple silicon support #2517 covers Apple Silicon builds.

Possible next steps:

1. Update the README's macOS section to say the cask is disabled and point people to the releases page, ideally with a note on opening the app past Gatekeeper.
2. If signing and notarizing the Mac builds is ever practical, that should let the cask be re-enabled. I understand from Dependency update: macOS release tracking issue #2548 and Provide DMG with universal/apple silicon support #2517 that the certificate cost and the planned next version may make this not worth doing for current pyfa.

Thanks for all your work on pyfa.