#50373: ci: update actions to node24
Merged
Description of Change
I noticed the following message in https://github.com/electron/electron/actions/runs/23278735986:
Node.js 20 actions are deprecated.
The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@5a3ec84eff668545956fd18022155c47e93e2684,
actions/upload-artifact@65462800fd760344b1a7b4382951275a0abb4808,
nick-fields/retry@7152eba30c6575329ac0576536151aca5a72780e.
Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026.
Please check if updated versions of these actions are available that support Node.js 24.
To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file.
Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true.
For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
This updates the actions that we can. nick-fields/retry currently doesn't have a release that supports node 24, tracking issue here: nick-fields/retry#162.
Checklist
- PR description included
- I have built and tested this PR
-
npm testpasses - PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.
Release Notes
Notes: none
Backports
39-x-y
PendingWaiting for a manual backport
40-x-y
PendingWaiting for a manual backport
41-x-y
PendingWaiting for a manual backport
42-x-y
In-flightSemver Impact
Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron