Phase 1 step 8 of VNCprodbuild. New workflow, additive to the existing
docker-publish*.yml/standalone-release.yml (which only ever built the
Docker image / standalone tarball, never the desktop shell).
Matrix over macos-latest/windows-latest/ubuntu-latest. Each leg: npm ci,
build:standalone, build:electron, then npm run test:electron (the Phase 1
step 2 smoke test) as a REQUIRED gate before packaging or any
artifact-upload step - a platform-specific regression fails the leg it
breaks instead of slipping through because only one OS was ever
smoke-tested. Linux needs an explicit Xvfb install first (no display
server on that runner by default); macOS/Windows runners have one.
Triggers on release-published (packages + publishes to that release via
electron-builder's --publish always, matching standalone-release.yml's
`gh release upload` precedent but through electron-builder's own GitHub
publish provider) and workflow_dispatch (packages only, uploads a build
artifact instead, --publish never).
Ships unsigned - CSC_IDENTITY_AUTO_DISCOVERY: "false" stops electron-builder
from probing for a macOS identity that doesn't exist (VNCprodbuild step 9:
no Apple Developer ID or Windows cert yet, both human-owned purchases).
Structured so signing needs no rewrite later - just add CSC_LINK/
CSC_KEY_PASSWORD (macOS) and/or WIN_CSC_LINK/WIN_CSC_KEY_PASSWORD (Windows)
as repo secrets once those exist.
Bernd Rodler
0bb098438a