Open
Description
Recommendation: A, a paid Apple Developer ID ($99 a year), so the fork's Mac app is signed and notarized like upstream's.
Context: the fork's Mac app is built unsigned (fork #2). macOS then asks "Open anyway" on install, and the app cannot update itself (macOS's updater only accepts a signed app whose new version has the same signature). Upstream signs its Mac app with its own Apple certificate, which the fork cannot use.
The question: how should the fork's Mac app be signed?
- A. Apple Developer ID (recommended). You join the Apple Developer Program ($99/year) and make a "Developer ID Application" certificate. You add it, plus an app-specific password for notarizing, as secrets on the fork repo (I give you the exact steps; agents never see the values). The fork's release workflow then signs and notarizes the Mac app. Result: installs like any app, updates itself, and macOS keeps its permissions (screen, files, keychain) across updates.
- B. Free workaround. No Apple account. The fork installs and updates the Mac app with its own small updater that downloads the release, checks it against a checksum file signed by the fork's release workflow, and swaps the app in place (files downloaded this way get no "Open anyway" prompt). Cost: about 3 security-critical PRs to carry. macOS may ask again for permissions it had already granted (screen recording, accessibility, keychain) after every update, because the app's signature changes each time.
- C. Keep it as is. Install by hand and click "Open anyway" each time.
Metadata
Metadata
Assignees
Labels
No labels
Activity
scuttletoby commentedon Nov 21, 2026
Owner decision (in chat, 2026-11-21): A (Apple Developer ID) is the choice, but the owner joins the program later, likely January 2027, because of the cost.
Until then: C. Stopgap so the owner does not click through prompts: an agent on the Mac installs and updates the fork's Mac app from the command line (download the release with
gh/curl, which leaves no quarantine flag, check the checksum, copy into Applications). No new fork code for this.Keeping this issue open; it is picked up again when the owner has the certificate, and then the agent gives the exact steps for the repo secrets.