Apple Code Signing & Notarization for Tauri Desktop App

I need an experienced DevOps engineer to configure Apple code signing and notarization for a Tauri 2.x desktop application, integrated into an existing GitHub Actions CI/CD pipeline. The app builds successfully but I need the signing and notarization layer added so the macOS .dmg installs without Gatekeeper warnings. --- What You'll Do 1. Configure Apple Developer ID certificates (Developer ID Application + Developer ID Installer) in my Apple Developer account 2. Set up GitHub Secrets for signing credentials (certificate .p12, password, Apple ID, team ID, app-specific password for notarytool) 3. Update my existing `release-desktop.yml` GitHub Actions workflow to: - Sign the Tauri macOS build with Developer ID certificate - Notarize using Apple's `notarytool` - Staple the notarization ticket to the .dmg - Upload the signed+notarized .dmg to GitHub Releases 4. Test the full pipeline: push a git tag → Actions builds → signed .dmg appears in Releases 5. Provide brief documentation of what was configured (secrets, cert expiry dates, renewal steps) --- Requirements - Proven experience with Apple code signing and notarization (not just iOS — specifically macOS Developer ID signing for direct distribution outside the App Store) - Experience with GitHub Actions CI/CD - Familiarity with Tauri, Electron, or similar framework build pipelines (Tauri uses `tauri-action` for builds) - Comfortable working on a feature branch with PR-based workflow --- Nice to Have - Experience with `tauri-action` specifically - Experience with universal macOS binaries (arm64 + x64) - Familiarity with macOS `.dmg` creation and customization --- Not In Scope - Windows code signing or Linux builds - Auto-updater configuration - Any application code changes - App Store submission (this is direct distribution only) --- How to Apply Please include in your proposal: 1. A brief description of a previous macOS code signing + notarization project you completed 2. Whether you've worked with Tauri or similar Rust-based desktop frameworks 3. Your estimated timeline for completion 4. Any questions about the scope