ci(release): sign & notarize macOS apps#1
Open
FahrenheitResearch wants to merge 1 commit into
Open
Conversation
The release workflow shipped the macOS .app with only Rust's automatic
ad-hoc signature, so Gatekeeper blocked every downloaded copy
("can't verify the developer / is damaged").
Add a macOS-only step that, when signing secrets are present:
- imports the Developer ID Application cert into an ephemeral keychain
- codesigns BowEcho.app with hardened runtime + a secure timestamp
- notarizes via the App Store Connect API key and staples the ticket
- packages the signed/stapled app and scrubs secrets from disk
Falls back to an unsigned zip (with a warning) when secrets are absent
so forks/PRs still build. Requires repo secrets:
MACOS_CERTIFICATE_BASE64, MACOS_CERTIFICATE_PWD, ASC_API_KEY_BASE64,
ASC_KEY_ID, ASC_ISSUER_ID.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Why
The release workflow shipped
BowEcho.appwith only Rust's automatic ad-hoc signature. macOS Gatekeeper rejects that on any downloaded copy ("can't verify the developer" / "is damaged"), which is why the v0.1.0 macOS downloads wouldn't open.What
Adds a macOS-only Sign and notarize step to
release.ymlthat:Developer ID Applicationcert into an ephemeral keychaincodesigns with hardened runtime + a secure timestamp.appand scrubs secrets from disk afterwardIf signing secrets are absent (e.g. fork PRs) it falls back to an unsigned zip with a warning, so builds don't break.
Required repo secrets (already configured)
MACOS_CERTIFICATE_BASE64,MACOS_CERTIFICATE_PWD,ASC_API_KEY_BASE64,ASC_KEY_ID,ASC_ISSUER_IDAfter merge
Push a new tag (e.g.
v0.1.3) and the macOS artifacts will come out signed + notarized automatically — no manual step. The already-publishedv0.1.0assets were fixed by hand and are unaffected.🤖 Generated with Claude Code