Skip to content

Code-sign and notarize macOS releases #22

Description

@sam-powers

The v0.1.0 .dmgs are unsigned, so every first launch is blocked by Gatekeeper and users must right-click → Open (documented in the README and User Guide, but it's real friction — and it looks untrustworthy).

Work

  1. Enroll in the Apple Developer Program ($99/year) — prerequisite for everything below.
  2. Create a Developer ID Application certificate; export as .p12.
  3. Add secrets to the repo and wire them into .github/workflows/release.yml — tauri-action supports this natively:
    • APPLE_CERTIFICATE / APPLE_CERTIFICATE_PASSWORD (signing)
    • APPLE_ID / APPLE_PASSWORD (app-specific) / APPLE_TEAM_ID (notarization)
  4. Tauri handles signing + notarization + stapling during tauri build when those env vars are present — no workflow restructuring expected.
  5. Remove the Gatekeeper workaround sections from README.md and docs/USER_GUIDE.md once verified.

Acceptance

A fresh download of the release .dmg opens on a clean macOS machine with no Gatekeeper bypass.

Blocked on: Apple Developer enrollment (maintainer action).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions