Sign releases with Developer ID and notarize them - #3
Merged
Merged
Conversation
build-app.sh enables the hardened runtime and a secure timestamp for Developer ID identities. scripts/release.sh builds a universal app, signs it, notarizes and staples it, and publishes the GitHub release with the zip. The signing key stays on the Mac instead of in CI secrets, so CI now only builds and tests. Claude-Session: https://claude.ai/code/session_0115d7b3mfRT6Gs8mgqtAt1x
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
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.
Releases so far were ad-hoc signed and not notarized, so Gatekeeper blocked the first launch and users had to click "Open Anyway". This PR matches Reprise: Developer ID signing, hardened runtime, notarization and stapling.
scripts/build-app.sh: a Developer ID identity (orHARDENED_RUNTIME=1) adds--options runtime --timestamp.scripts/release.sh vX.Y.Z:notarytoolusing a keychain profile (macTreeby default), then staples the ticket and checks it withspctl.MacTree-vX.Y.Z.zipand prints the SHA-256 for the Homebrew cask.build.yml: drops thereleasejob. The signing key stays on the Mac rather than in CI secrets, so CI only builds and tests.Tested locally:
flags=0x10000(runtime)and a secure timestamp on the universal binary.spctlreports "Unnotarized Developer ID" until notarization, as expected.release.shexits early without creating a tag when the profile is missing.https://claude.ai/code/session_0115d7b3mfRT6Gs8mgqtAt1x