| name | electron-release |
| description | Use when an accepted Electron work item needs packaging configuration, versioning, signing/notarization readiness, artifact checks, update metadata, or a Windows/macOS/Linux release matrix. Do not use to publish, upload, or claim unrun platform builds. |
Electron Release
Prepare and verify packages without turning readiness into publication authority.
- Read sidecar integration task evidence, review findings,
references/release-standard.md, and references/release-matrix.md.
- Detect the existing builder, scripts, targets, architectures, native rebuild, ASAR/fuses, update provider, and CI. Preserve established choices.
- Record version, changelog, migrations, backup/rollback, channels, and minimum OS/runtime support.
- Require complete declared frontend/backend deliverables and integration
verification before release readiness. Run only package/smoke commands that
exist in the target repository and are in the authorized scope.
- Record secret variable names as
PRESENT/MISSING only; never print values.
- Build official artifacts on matching runners when required, then record command/run, signing/notarization, checksum, and smoke evidence per target.
- Attach readiness or blockers to the integration task Result; use
NOT RUN
for missing platform evidence.
Do not create a formal Release, upload an installer, publish a package, alter signing credentials, or infer another platform's success.
