Electron Production Build & Release Guide

This skill provides enterprise-grade best practices for building, signing, releasing, and distributing Electron applications with emphasis on security, reliability, performance, and user trust.

Quick Reference

1. Build Configuration: For electron-vite production config, bundle optimization, and pre-build checks.
2. Code Signing: Platform-specific signing for Windows (EV certificates), macOS (Developer ID + notarization), and Linux (GPG).
3. Auto-Updates: electron-updater configuration, staged rollouts, and update testing.
4. Release Workflows: GitHub Actions CI/CD pipelines for multi-platform builds.
5. Distribution: GitHub Releases, Cloudflare R2, or private server hosting.

Core Principles

• Security First: All production builds must be code-signed; macOS builds must be notarized.
• Pre-Build Verification: Always run pnpm audit, pnpm run typecheck, pnpm run lint, and pnpm run test before builds.
• Semantic Versioning: Follow SemVer strictly (MAJOR.MINOR.PATCH).
• Staged Rollouts: Release to a percentage of users first, then expand gradually.