electron-app-deployment

Automating Electron app deployment across platforms requires a CI/CD pipeline that handles building, signing, notarizing, and releasing. This Skill integrates with GitHub Actions to manage multi-platform packaging and auto-update configuration end-to-end.

Setting up Electron code signing and notarization requires valid signing certificates and notarization credentials, particularly for macOS. This Skill automates the verification and integration of these credentials within your configured build setup.

Yes, this Electron deployment workflow supports both Electron Forge ForgeApp and Electron Builder BuilderApp toolchains. It automates builds, signings, and notarizations across supported platforms for either configuration.

Configuring CI/CD pipelines for Electron app releases involves setting up GitHub Actions secrets and defining build configurations in forge.config.ts or package.json. This Skill uses those credentials and configurations to automate the release workflow.

Yes, you need access to GitHub Actions secrets or equivalent CI secrets to run the Electron build and sign pipeline. These secrets securely store the signing certificates and notarization credentials required for automated deployment.

Electron app notarization in CI can fail if signing certificates or notarization credentials are missing or incorrectly configured. This Skill requires properly configured GitHub Actions secrets and a valid build setup to execute notarization successfully.