-
Notifications
You must be signed in to change notification settings - Fork 964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update supported Node versions for JavaScript Composite Actions #2255
Comments
I did not know of https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ prior to opening this issue & #2257 Even if forcing the move to Node16 is a good idea, if it's done for the 1st day of Summer, it will give users less than a quarter with a maintained NodeJS version. I understand tho that dropping Node12 so suddenly would be a bit... uncouth. (especially given your prior announcement) I'd propose adding support for Node18 for now, and instead of "migrate all actions to run on Node16 by Summer 2023.", I think you should skip Node 16 and go straight to 18. When dropping Node 12 in Summer '23, it'll be interesting to add support for Node 20, given that it'll be the Active LTS just a quarter later. |
Hello @louis-bompart, thanks for taking an interest in keeping the runner up-to-date. We bundle all supported Node versions in the release archive, so it's not feasible to add too many newer versions. Tentative look to the future: As you know, Node 12 in the runner is being deprecated, I would expect the same time we finally drop it we will introduce a new LTS Node version - likely Node 20. |
@fhammerl now that all the runner images are using Node 18, would it be possible to add Node 18 as an option for Javascript Composite Actions? It'd be really great to get actions/github-script#310 |
You mentioned in #2255 (comment) about supporting Node.js 20 was released today, April 18, 2023 - see Node v20.0.0 (Current). |
Also submitted to https://github.com/orgs/community/discussions/53217 |
@fhammerl Is there a more concrete date at which we can roughly expect a Node 20 runtime for JavaScript GitHub Actions will be available? The support window for Node 16 is slowly coming to a close and it would be excellent to be able to use a more up to date runtime version in our JavaScript GitHub Actions. |
JFYI potential ugly temporary workaround for action authors: https://github.com/orgs/community/discussions/53217#discussioncomment-6227341 |
Describe the enhancement
Currently, JavaScript composite actions only support Node 12 and 16.
Node 12 is deprecated and Node 16 has an accelerated EoL. So arguably, none are viable choices for long-term development.
I would propose removing support for Node 12 and adding support for 18 (current Active LTS).
The text was updated successfully, but these errors were encountered: