Skip to content

Electron Packaging And Suite ​

Packages are built unsigned, with the keychain untouched, and only when the director asks for a build. Day-to-day verification runs on the suites and the captures. A packaged suite launches the built app from a copy outside the project, where nothing resolves back into the project's node modules, and checks every platform's package for the shell and the website next to it.

Why ​

A package works away from the repository, and the packaged suite proves it on the build machine.

How To Apply ​

  • A package that only works next to the repository's node modules breaks on every other machine. Building on request keeps the loop fast.
  • A version guard refuses to package a version that is tagged already. A packaged build carries the version of its commit.
  • All platform packages build from one machine where the packager allows it. When the app has no auto updater, its side files can go.
  • The packaged suite probes what breaks silently in a package: the fonts, the icons, the store path.
  • A build that goes out is signed, and on a Mac notarized, by the build itself in CI, from a certificate and an API key held as the CI's secrets, never through the director's keychain (Keep Secrets Away From Agents). An unsigned build may not open on another machine.
  • A release checklist names the steps around such a build: the debug tools stripped, the signing and notarization, the platforms tested by hand.