You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release DMGs are currently ad-hoc signed. Because of that, macOS blocks the first launch of a downloaded copy, and people have to open System Settings › Privacy & Security and click Open Anyway once.
The packaging from #3 already handles signing. Once the credentials exist, turning it on means adding repository secrets, with no code changes.
To do
Join the Apple Developer Program ($99/year).
Create a Developer ID Application certificate and export it as a .p12.
Create an app-specific password for the Apple ID.
Add the repository secrets: MACOS_CERTIFICATE (base64 .p12), MACOS_CERTIFICATE_PASSWORD, MACOS_SIGN_IDENTITY, APPLE_ID, APPLE_TEAM_ID, APPLE_APP_PASSWORD. The README's "Releases" section has the details.
Tag a release and confirm spctl --assess accepts the DMG and that a downloaded copy opens with no warning.
Remove the "Open Anyway" note from the README and release notes.
Done. v0.2.2 is the first signed and notarized release, built by this run after #8. Since #8, a release build with signing secrets fails if notarization fails, so a green run means Apple notarized the DMG.
Activity
banstack commentedon Oct 26, 2026
Done off the back of #8, closing
banstack commentedon Oct 26, 2026
Done. v0.2.2 is the first signed and notarized release, built by this run after #8. Since #8, a release build with signing secrets fails if notarization fails, so a green run means Apple notarized the DMG.
Generated by Claude Code