Repository navigation
Support node22 in runs.using for JavaScript actions #3600
Description
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)
Reacted by andyl-ioki, Verena Brodbeck, j-nix, Lars Berger, electrovir, Daren McCulley, Roger Studner, Masafumi Koba, SvenStaehs, Dmitri Samoilov and 57 more
Reacted by Aliaksei Sapach, Dipak Parmar, Roger Studner, Thierry D., Michael Duane Mooring, Richard Hagen and Andrew Brennan
Activity
dipakparmar commentedon Dec 5, 2024
+1 for this.
iamstarkov commentedon Dec 22, 2024
this would be lovely because node22 had been LTS for some time now
fix: Downgrading to `node20` since `node22` is not supported yet
albertodiazdorado commentedon Feb 4, 2025
+1
runspired commentedon Feb 8, 2025
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 😭
dropping to node20
switch to better-sqlite3 because of actions/runner#3600
switch to better-sqlite3 because of actions/runner#3600
drop node22 because of actions/runner#3600
MikeMcC399 commentedon Mar 12, 2025
node22supportMikeMcC399 commentedon Mar 25, 2025
@nebuk89
In https://github.com/actions/runner/discussions/2704#discussioncomment-12016947 you wrote
Do you (or anybody else) have any news for us about your concrete plans and timelines?
garysassano commentedon Jun 2, 2025
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 commentedon Jun 2, 2025
8 remaining items
MikeMcC399 commentedon Aug 13, 2025
@salmanmkc
Thanks for the "big picture" of all the work you're doing!
jackylamhk commentedon Aug 13, 2025
@salmanmkc Thanks for the update! Are there plans to make Node 22 available or will it be skipped?
salmanmkc commentedon Aug 13, 2025
No worries! Will be skipped
CatsMiaow commentedon Sep 22, 2025
https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Node.js v24 Active LTS Start
2025-10-28salmanmkc commentedon Sep 22, 2025
Yeah that's the blog post, node 24 is supported as of v2.327.1 however, using v2.328.0 will allow you to start testing with environment variables as outlined in the blog post.
MikeMcC399 commentedon Oct 1, 2025
and https://docs.github.com/en/actions/reference/workflows-and-actions/metadata-syntax#runs-for-javascript-actions already documents
with
node22already officially skipped.fix: update to use node 22 in actions (#269)
iamstarkov commentedon Oct 27, 2025
@salmanmkc I've asked it somewhere else, but I'll repeat it here for exposure.
Do you plan to skip nodejs 26?
MikeMcC399 commentedon Dec 4, 2025
@salmanmkc
Do you have any overview of which GitHub JavaScript actions still need to be migrated to
node24?The announcement Deprecation of Node 20 on GitHub Actions runners said
Going by that, I'd expect the migration to be complete or almost complete by now, however there are actions like https://github.com/actions/upload-artifact that are still on
node20.Could you share any new plans for the remainder of the migrations?
ChristopherHX commentedon Dec 4, 2025
Trivia https://github.com/actions/upload-artifact/releases/tag/v5.0.0 claims to contain the node24 update as breaking change, but the PR to bump to node 24 was never merged and all CI checks from 3 month ago are all red 🤣.
Could really got marked internally as done.
salmanmkc commentedon Dec 12, 2025
Download artifact, upload artifact and cache are all on node 24 now.
There are a few actions that my PRs haven't all been reviewed or I need to chase/revisit, however the main actions that we provide are all upgraded to node 24 now.
salmanmkc commentedon Dec 12, 2025
All the CI checks were red because I was referencing a a local package similar to how you do npm link, that's done for testing, once that is done I switched it over to published packages and it went green.
As per v5, a release was done by the team as they were shipping some other changes and that included the toolkit changes which were done for node 24 support.
salmanmkc commentedon Dec 12, 2025
Closing this as we have node 24 support now, see this post for more details https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/