GeezerVison

Summary

Closes the remaining gap in the release pipeline, without maintaining a second copy of the target configuration.

• electron-builder.js now registers artifactBuildCompleted and afterAllArtifactBuild:

  • artifactBuildCompleted records every platform:target that emitted an artifact.
  • afterAllArtifactBuild walks buildResult.platformToTargets — the targets electron-builder actually planned — and throws for any target that never emitted one.

  The check reads the same file the packager reads, so adding or removing a target needs no matching change here. Only dir is skipped, because it produces the unpacked app rather than something to upload.

• upload-artifact uses if-no-files-found: error instead of the default warning, with !dist/*/ excluding directories — so a job that only produced an unpacked app fails instead of uploading nothing.

• publish-release refuses to publish a draft with no assets, so an empty release can never go out.

Why

verifyPackagedDependencies and verifyFuses both stop at the unpacked app. Electron can pack successfully and still fail to build a distributable, and upload-artifact treats an empty match as a warning — so a platform job could go green with nothing to download, and the release would still publish. That is precisely the failure mode that left a sibling project without Windows installers for seven releases.

Notes

• No target→extension table: the hook compares produced artifacts against the planned targets, so dmg/zip/exe/AppImage/deb/rpm are covered implicitly and a new target is covered automatically.
• Verified the hooks with simulated electron-builder payloads: all targets emitting passes; a missing RPM fails with electron-builder produced no artifact for: linux/rpm; nothing emitting names every planned target; a dir-only build passes the hook and is then stopped by the upload guard.
• actionlint passes on both workflows; no packaged-app or runtime changes.