Skip to content

ci: fix 504 Electron download timeout and upgrade to Node 22#149

Merged
NeuroKoder3 merged 2 commits into
mainfrom
fix/ci-node22-electron-skip-binary
Jun 9, 2026
Merged

ci: fix 504 Electron download timeout and upgrade to Node 22#149
NeuroKoder3 merged 2 commits into
mainfrom
fix/ci-node22-electron-skip-binary

Conversation

@NeuroKoder3

Copy link
Copy Markdown
Owner

Problem

All three failing checks hit the same root cause:
pm ci\ triggers Electron's postinstall script which downloads a ~100 MB binary from GitHub releases. That request times out with a 504 Gateway Timeout.

Additionally, @electron/notarize, @electron/rebuild, and
ode-abi\ all require >=22.12.0\ but every job was running Node 20.

Changes

*\ci.yml*

  • Upgrade Node 20 → 22 across all jobs
  • \ELECTRON_SKIP_BINARY_DOWNLOAD=1\ on \�uild\ and \�uild-windows\ (neither launches Electron)
  • \�ctions/cache@v4\ on ~/.cache/electron\ in the \e2e\ job (needs the binary, cache survives future flakiness)
  • \cache: 'npm'\ on all \�ctions/setup-node\ calls

*\security.yml*

  • Upgrade Node 20 → 22 across all jobs (audit, snyk, lint, test-security, load-test, lockfile-check)
  • \ELECTRON_SKIP_BINARY_DOWNLOAD=1\ on \ est-security\ and \load-test\ — fixes the two failing Security Scanning checks
  • \load-test\ switched from
    pm install\ to
    pm ci\ for deterministic installs
  • \cache: 'npm'\ everywhere

*
elease.yml*

  • Upgrade Node 20 → 22 on build-windows, build-macos, and gate jobs
  • \ELECTRON_SKIP_BINARY_DOWNLOAD=1\ on \gate\ (does not launch Electron)
  • \cache: 'npm'\ everywhere

…here not needed, cache electron binary in e2e job

Co-authored-by: Cursor <cursoragent@cursor.com>
@NeuroKoder3 NeuroKoder3 enabled auto-merge (squash) June 9, 2026 02:37
…e binary

Co-authored-by: Cursor <cursoragent@cursor.com>
@NeuroKoder3 NeuroKoder3 merged commit 24f5fd0 into main Jun 9, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant