Repository navigation
ci(release): sign with Developer ID and notarize the darwin binaries - #48
Merged
Merged
Conversation
scripts/sign-darwin.sh is now the single signing path (Makefile and the
goreleaser post-build hook):
- MARINA_SIGN_IDENTITY set: Developer ID, hardened runtime, secure timestamp,
virtualization entitlement; with NOTARY_* also set, notarytool submit
--wait and fail on anything but Accepted (printing the notary log).
- unset: ad-hoc, as before.
release.yml imports the certificate into a temporary keychain (as Pastiche
does), checks the secrets and notary credentials up front, verifies each
binary's team ID, entitlement and Gatekeeper verdict ("Notarized Developer
ID"), and gains workflow_dispatch: a snapshot run that signs and notarizes
but publishes nothing.
make build picks the keychain's Developer ID identity when present.
Verified locally: a Developer ID + hardened-runtime build starts a VM, and
goreleaser's hook inherits MARINA_SIGN_IDENTITY for both architectures.
Co-Authored-By: Claude Opus 5.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
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.
Signs release binaries with the Developer ID certificate (team
PZARL6555S) and notarizes them, using the same secrets and keychain steps as Pastiche.Why: a stable team ID that an MDM/EDR allowlist (Kandji, Falcon) can trust across releases, and no Gatekeeper friction on managed Macs. Not a fix for the data path: measured on a Mac with Falcon 8.10 + Kandji, Apple-signed and ad-hoc clients alike reach the lima0 IP and MetalLB VIPs.
scripts/sign-darwin.shNOTARY_*set; ad-hoc when no identity.goreleaser.yamlrelease.ymlspctl→ "Notarized Developer ID"),workflow_dispatchsnapshot runMakefilemake builduses the keychain's Developer ID when presentVerified locally: a Developer ID + hardened-runtime build starts a VM;
goreleaser build --snapshotsigns both architectures with the team ID and entitlement.Before the next tag: set the five secrets (same names as Pastiche), then
gh workflow run release.ymlto test notarization without publishing.🤖 Generated with Claude Code