devsyncwrld
b4d001eb26
OpenSSF Scorecard / Scorecard analysis (push) Waiting to run
CI / Build & test (Node 20) (push) Canceled after 0s
CI / Build & test (Node 24) (push) Canceled after 0s
CI / Build & test (push) Canceled after 0s
CodeQL / Analyze (javascript-typescript) (push) Canceled after 0s
Security / Secret scan (gitleaks) (push) Canceled after 0s
Security / Dependency scan (OSV-Scanner) (push) Canceled after 0s
Security / IaC/config scan (Trivy) (push) Canceled after 0s
Security / License compliance scan (Trivy) (push) Canceled after 0s
release.yml builds four platforms and publishes a release, which is right for a release and slow for 'give me an exe to test'. Wall time is set by the Windows job, which compiles native modules and downloads Electron twice because it targets x64 and arm64 together — and Windows-on-ARM is not something this group runs. This path builds one architecture, caches the Electron and electron-builder downloads (~100MB re-fetched every run otherwise), and uploads the installer as an artifact, so it needs neither a tag nor a version bump. Kept as a separate file: release.yml comes from upstream and takes merges, so editing it would conflict on every update. Cost matters too on a private repository: macOS runners bill at 10x and Windows at 2x, so the full matrix was paying for macOS builds on every tag.