GitHub Community
Will node22 still be supported by actions runners after the fall of 2026? #193558
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
You're good. The migration to Node 24 refers to the runner's internal software, not the Node version available for your code. Since Node 22 is the current LTS, it will definitely still be supported in the tool cache. You can just keep specifying actions/setup-node with version 22 in your workflows and you'll be fine. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the answer! |
Beta Was this translation helpful? Give feedback.
-
|
If you just need Node 22 to execute a script or command in a workflow step, you are completely fine! You can safely continue using actions/setup-node@v4 with node-version: 22. Node 22 is an LTS release, so GitHub will keep it available in the runner tool cache for a very long time. If you meant you are authoring a custom JavaScript action (e.g., using runs: using: 'node22' inside an action.yml file), you are also safe. GitHub always provides a massive, multi-year deprecation window before they drop support for older Node runtimes in custom actions. It definitely won't suddenly break in the fall of 2026 just because Node 24 is introduced. |
Beta Was this translation helpful? Give feedback.
-
|
Solid point, Lalit. That distinction for custom actions is key—authors always worry about the runtime breaking, so good catch on clarifying that deprecation window. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
You're good. The migration to Node 24 refers to the runner's internal software, not the Node version available for your code.
Since Node 22 is the current LTS, it will definitely still be supported in the tool cache. You can just keep specifying actions/setup-node with version 22 in your workflows and you'll be fine.