Repository navigation
MacOS Code Signing
| Mode | When | Credentials | Apple contacted | Result |
|---|---|---|---|---|
| A — Development | pull requests, forks | none | no | apps ad-hoc signed (required on Apple silicon), labelled development builds |
| B — Pipeline test |
macos-signing-test.yml (manual, or on changes to the signing code) |
macos-signing-dummy.env + ephemeral self-signed identity |
no |
MOCK — NOT SIGNED OR NOTARIZED; cannot publish |
| C — Production | release tags v*, and main (latest) and staging (dev_build) in mne-tools/mne-cpp |
the APPLE_* secrets |
yes | Developer ID signed, notarized, stapled, verified, then published |
Production (release-macos.yml, release-installer.yml):
-
macos_signing.py check-credentials --mode productionrejects missing, malformed orTEST_ONLYvalues before anything is built into a release. -
macos-codesign-setupimports the.p12into a temporary keychain and selects the one trusted Developer ID Application identity whose Team ID equalsAPPLE_TEAM_ID. -
deploy.shdeploys Qt and the MNE-CPP libraries into the bundles, thenmacos_release_signing.sh treesigns every Mach-O file, framework and app inbin/andlib/inside-out (no--deep) with the hardened runtime and a secure timestamp, verifies the Apple chain, Team ID and timestamp of each, notarizes them withxcrun notarytool submit --wait, and staples the apps. The tarball, the.dmgand the installer payload therefore contain the same notarized code. - The
.dmgis signed, notarized, stapled and assessed withspctl --type open. - The installer job verifies that its payload carries the same team's signatures and
stapled tickets, signs the QtIFW installer app after
binarycreator, notarizes and staples it, then does the same for its.dmg. -
require-production-evidencelets the upload run only if Apple returnedAcceptedfor every submission. A rejection prints the notarization log and fails the job.
Entitlements: none. With one Developer ID, all frameworks and plugins share the Team ID,
so the hardened runtime's library validation accepts them; a run with library
validation relaxed showed MNE Scan loading every plugin. App data lives in
Contents/Resources, so its signatures are stored in the bundle seal and survive
archiving.
The static macOS archives are not Developer ID signed; the release notes say so.
MACOS_SIGNING=unavailable is the only way to release without Apple signing, and the
release verification then requires the release notes to record it.
- Repository secrets
APPLE_APPLICATION_CERT_BASE64,APPLE_APPLICATION_CERT_PASSWORD,APPLE_ID,APPLE_ID_PASSWORD(app-specific password) andAPPLE_TEAM_IDset;APPLE_INSTALLER_CERT_BASE64,APPLE_INSTALLER_CERT_PASSWORD(only for a flat.pkg) andAPPLE_KEYCHAIN_PASSWORDunset. - Repository variable
MACOS_SIGNINGdeleted. - Workflow permissions stay read-only by default; secrets are never passed to
pull-request workflows, and
macos-signing-test.ymlreads no secret. - Environment
releasekeeps its required reviewer; it gates the Release Candidate approval.
MNE-CPP — BSD-3-Clause licensed · Maintained by the MNE-CPP authors · Website · API · Source
Edit this wiki via
doc/wiki/— direct edits in the GitHub UI are overwritten on next push tomain.