build: notarized developer id signing - #33
Merged
Conversation
Notarization rejects binaries without the hardened runtime; hardened runtime in turn strips mic capture and Apple Events unless re-granted via entitlements. Sparkle's nested XPC services are signed individually (each must carry the runtime flag). Ad-hoc dev builds keep the old path. 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.
Wires up the Tutor Intelligence Apple Developer account (Team S52X7AGB2P).
Autoupdatehelper binary is what the first notarization attempt rejected.Proven end-to-end before merge: a locally built bundle with this exact recipe was submitted to Apple's notary service — status: Accepted (submission
9d83e166, first-ever from this team, ~40min extended scan; subsequent runs should take minutes). All five repo secrets are set.After the first signed release: cask drops the quarantine postflight; users re-grant mic + accessibility once (signature identity changes ad-hoc → Developer ID), then permissions survive all future updates.
🤖 Generated with Claude Code