Sign and notarize macOS release builds - #18
Open
mohnjiles wants to merge 1 commit into
Open
Conversation
Pass Developer ID signing + notarization credentials to tauri-action so macOS builds are no longer ad-hoc signed (Gatekeeper rejected them as "damaged" on download). 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.
What
Passes Developer ID signing + notarization credentials to
tauri-actionin the release workflow, so macOS builds stop being ad-hoc signed. Currently every macOS download fails Gatekeeper with the misleading "LitePost is damaged and can't be opened" dialog (v0.5.0 aarch64 confirmed:Signature=adhoc,TeamIdentifier=not set).Setup required before merging
The workflow references the same secret names the Stability Matrix release pipeline uses. They currently live as repo secrets on StabilityMatrix, so they need to be made available here — either promote them to org-level secrets (recommended) or copy them into this repo:
PROD_MACOS_CERTIFICATE(base64 .p12)PROD_MACOS_CERTIFICATE_PWDPROD_MACOS_CERTIFICATE_NAME(theDeveloper ID Application: …identity string)PROD_MACOS_NOTARIZATION_APPLE_IDPROD_MACOS_NOTARIZATION_PWD(app-specific password)PROD_MACOS_NOTARIZATION_TEAM_IDNo keychain-password secret is needed — Tauri creates its own ephemeral keychain. Tauri v2 enables hardened runtime by default once a signing identity is set, so no
tauri.conf.jsonchanges are needed.Note: notarization adds a few minutes to each of the two macOS matrix jobs.
🤖 Generated with Claude Code