Supporting Node.js 14 and 16 LTS as the runtime of JavaScript action
See original GitHub issueDescribe the enhancement
Node.js v14.15.0 has been released and the 14.x release line now moves into Active LTS. Can the GitHub Actions runner support it as the runtime of a JavaScript (TypeScript) action? Is there a roadmap for this?
Code Snippet
Today, we can set node12
to runs.using
.
runs:
using: 'node12'
main: 'main.js'
Can we set node14
(or node16
) as follows?
runs:
using: 'node14'
main: 'main.js'
Additional information
We also need to update the documentation when node14
is available.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:103
- Comments:22 (4 by maintainers)
Top Results From Across the Web
Node.js 16.x runtime now available in AWS Lambda
The Node.js 16 runtime includes support for ES modules and top-level await that was added to the Node.js 14 runtime in January 2022....
Read more >Actions can now run in a Node.js 16 runtime
Actions authors can now specify that their action can run in Node.js 16 by specifying runs.using as node16 in the action's action.yml ....
Read more >Node v16.14.1 (LTS)
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Read more >Drop of Node.js 12 support and deprecation of Node.js 14 ...
The currently supported Node.js LTS version is 16. We urge all users not already on Node.js 16 to upgrade as soon as is...
Read more >Migrate to Node.js 16
Actions is designed to support multiple versions of node concurrently, and currently supports both Node 12 and Node 16. In addition, no-code ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
Top Related Hashnode Post
No results found
Top GitHub Comments
Node 14 or 16 would be great for my action here since it uses an ES module and it’s not trivial to get that running under Node 12.
I’m not sure if this is what is being suggested, but please don’t make us wait until after October. I have so much code that requires v14 because of optional chaining.