macos-signing-notarization

What problem does it solve?

This Skill solves the CI reliability problem of producing macOS Electron artifacts that are both correctly code signed and accepted by Gatekeeper through Apple notarization, avoiding slow or opaque built-in notarization steps.

Core Features & Use Cases

• Code signing for Electron artifacts: Uses a Developer ID Application certificate provided as base64 (p12) so the app bundle is signed deterministically by electron-builder during packaging.
• Apple notarization via App Store Connect API key: Submits, polls, and staples the DMG using xcrun notarytool with AuthKey.p8 generated at runtime from secrets, avoiding Apple ID/password and 2FA issues in CI.
• CI-friendly workflow steps with guardrails: Splits submit/poll/staple so you can see queue progress, applies a non-blocking notarization timeout, and ensures artifact release continues even if notarization is delayed.

Use case: You ship an Electron macOS app on every release and need a known-good workflow that handles certificate format pitfalls (legacy PKCS12), hardened runtime entitlements, and reliable notarization ticket stapling before uploads.

Quick Start

Add the three workflow steps (submit, poll, staple) after electron-builder packaging, using the required GitHub Actions secrets for the certificate and App Store Connect API key.