Support node22 in runs.using for JavaScript actions

[sergei-startsev]

Describe the bug

Specifying node22 as the runtime for JavaScript actions results in System.ArgumentOutOfRangeException error.

Node.js v22 transitioned into LTS On October 29, 2024

To Reproduce

runs:
  using: 'node22'
  main: 'main.js'

Expected behavior

• No errors.
• Documentation is updated.

Runner Version and Platform

• Current runner version: 2.321.0
• Operating System: Ubuntu 24.04.1 LTS

What's not working?

Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node22' is not supported, use 'docker', 'node12', 'node16' or 'node20' instead.')
   at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs)
   at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)

[dipakparmar]

+1 for this.

[iamstarkov]

this would be lovely because node22 had been LTS for some time now

[albertodiazdorado]

+1

[runspired]

seems like no one can use any of the great new node features in any actions until this is fixed as repo code run using an action is constrained to <= node 20 😭

[MikeMcC399]

• There is a long-running related discussion https://github.com/actions/runner/discussions/2704 although so far there hasn't been any response to the question of node22 support
• Node.js 22 is the Active LTS version until Oct 28, 2025 when the up-coming Node.js 24 is planned to take over the Active LTS role. Node.js 24's initial release is planned for Apr 22, 2025.

[MikeMcC399]

@nebuk89

In https://github.com/actions/runner/discussions/2704#discussioncomment-12016947 you wrote

Sorry for the slowness on what comes next after node20! I was out for a few months but now I am back I will pick up with the team and start the annual wheel turn of moving up our node versions 🗡

Do you (or anybody else) have any news for us about your concrete plans and timelines?

[garysassano]

In about 5 months, Node.js 24 will become the Active LTS version. Given the current pace, it seems unlikely this will be addressed before then. At that point, it might make more sense to update directly to Node.js 24 instead.

[MikeMcC399]

@garysassano

In about 5 months, Node.js 24 will become the Active LTS version. Given the current pace, it seems unlikely this will be addressed before then. At that point, it might make more sense to update directly to Node.js 24 instead.

We're really lacking any sort of response from the GitHub Actions organization at the moment. I'm unsure why this is.

It depends really on the strategy - whether each Node.js LTS is going to be supported, or whether there are going to be jumps, like from 20.x to 24.x. Preferably GitHub Actions should support each Node.js LTS version from when it is declared LTS until its End-of-Life transition.

Node.js	EOL
20.x	2026-04-30
22.x	2027-04-30
24.x	2028-04-30

Milestones from https://github.com/nodejs/Release