ST-2026-234 · Runtimes & developer platforms
GitHub moves the Actions Node 20 removal date to 23 September
GitHub's 25 August editor note changes the controlling GitHub Actions Node 20 removal date to 23 September 2026; runners have used Node 24 by default since 16 June, with the temporary Node 20 opt-out ending when the runner upgrade removes Node 20.
Previous state
GitHub Actions runners use Node 24 by default, while ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true can temporarily opt affected actions back to Node 20 pending its removal.
Current state
GitHub's August 25 editor note sets 23 September 2026 as the Node 20 removal date; after the corresponding runner upgrade the temporary Node 20 opt-out no longer restores that runtime.
Affected users
Who needs to care
GitHub Actions JavaScript actions and self-hosted-runner environments that still depend on Node 20 compatibility, including environments affected by Node 24's macOS 13.4-or-lower and ARM32 limitations.
Required response
What to do
Validate affected actions and self-hosted runners on Node 24 before 23 September 2026 and remove dependencies on the temporary Node 20 opt-out.
Evidence boundary
What the source does not prove
GitHub proves the amended 23 September removal date and the stated compatibility boundaries. It does not claim that Node 20 has already been removed before that date.
Lifecycle history
Dated event sequence
- Node 24 became the default runtime
GitHub Actions runners began using Node 24 by default for JavaScript actions.
- Removal date amended
GitHub added an editor note changing the controlling Node 20 removal date to 23 September 2026.
- Node 20 removal scheduled
The runner upgrade is scheduled to remove Node 20 and end the temporary opt-out.
Evidence ledger
First-party sources
- 01GitHub — Deprecation of Node 20 on GitHub Actions runners
Official GitHub Changelog editor note · 2026-08-25
Open official source ↗