A GitHub Action that automates building and releasing Electron apps across macOS, Windows, and Linux using electron-builder.
Electron Builder Action is a GitHub Action that automates the building and releasing of Electron applications. It uses electron-builder to package apps and publish them to platforms like GitHub Releases, enabling cross-platform CI/CD workflows without manual intervention.
Electron app developers who want to automate their build and release processes using GitHub Actions, especially those targeting multiple operating systems.
Developers choose this action because it simplifies the entire release pipeline, handling complex tasks like code signing, notarization, and multi-platform builds with minimal configuration, directly within GitHub's ecosystem.
:electron: GitHub Action for building and releasing Electron apps
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Builds Electron apps on macOS, Windows, and Linux runners in a single GitHub Actions workflow, as demonstrated in the matrix strategy example, eliminating the need for separate machines.
Supports macOS and Windows code signing via repository secrets, with detailed instructions for exporting and encoding certificates, ensuring secure app distribution.
Publishes artifacts to GitHub Releases automatically when commits are tagged with a version, streamlining the release process without manual intervention.
Allows configuration of build scripts, arguments, and directories through options like build_script_name and args, providing flexibility for different project setups.
Requires meticulous configuration of code signing certificates and notarization secrets, which involves exporting, encoding, and storing sensitive data, prone to errors.
Tightly coupled with GitHub Actions, making it unsuitable for teams using other CI/CD platforms without significant adaptation or duplication of effort.
Inherits all limitations and bugs from electron-builder; custom features or fixes may require workarounds or forking the action, as noted in the reliance on external docs.