Add a Makefile and a notarized release target - #6
Merged
Merged
Conversation
make release builds with the Developer ID identity and a secure timestamp, submits to the notary service, staples the ticket, and writes dist/Macstify.zip with a SHA-256 checksum.txt. The submitted zip and the distributed zip are separate files: stapling applies to the bundle, so the distributable has to be re-zipped after the ticket comes back. CODESIGN_IDENTITY is matched by prefix, so no name or team id is hardcoded. Both it and NOTARY_PROFILE can be overridden on the command line. Also commits what Xcode wrote while the project was open: automatic signing with a development team, and ENABLE_HARDENED_RUNTIME on the Macstify target. Notarization refuses a bundle without the hardened runtime, and Xcode sets it on both configurations - for a bundle that runs inside legacyScreenSaver rather than as its own process, the flag changes nothing at runtime either way. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
winebarrel
enabled auto-merge
August 9, 2026 08:49
winebarrel
added a commit
that referenced
this pull request
Aug 9, 2026
Add a Makefile and a notarized release target
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.
make releasebuilds with the Developer ID identity and a secure timestamp, submits the bundle to Apple's notary service, staples the returned ticket, and writesdist/Macstify.zipwith a SHA-256dist/checksum.txt.The submitted zip and the distributed zip are deliberately separate files. Stapling applies to the bundle, so the distributable has to be re-zipped after the ticket comes back — zipping once and submitting that same file would ship an unstapled bundle.
CODESIGN_IDENTITYis matched by prefix (Developer ID Application), so no name or team ID is hardcoded. Both it andNOTARY_PROFILEcan be overridden on the command line.Also in here
What Xcode wrote into
project.pbxprojwhile the project was open: automatic signing with a development team, andENABLE_HARDENED_RUNTIMEon the Macstify target. Notarization refuses a bundle without the hardened runtime.Xcode sets it on both Debug and Release. That's fine here — the flag governs a process, and this bundle runs inside Apple's
legacyScreenSaver, so it changes nothing at runtime either way.Verification
make build,make lint,make formatall pass.make -n releasereviewed; the signing half was run for real earlier and producedAuthority=Developer ID Application,flags=0x10000(runtime)and a secure timestamp.make releasesubmits to Apple, so the notarize/staple half is unverified.🤖 Generated with Claude Code
https://claude.ai/code/session_01MVZKaTdW5LpcwGnwAV22ZV