-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Node 16 deprecation #850
Comments
Hello, @kinano! Thank you for creating an issue, we'll look into this :) |
Based on the announcement GitHub Actions: Transitioning from Node 16 to Node 20 the current version of this JavaScript Action v3.8.1 will cause So apart from the fact the Node.js Please release a new version supporting |
Hello @MikeMcC399! Thank you very much for your input, we are looking into this :) |
This comment was marked as outdated.
This comment was marked as outdated.
|
This major version mainly involves not using Node.js 16 internally anymore, which will be end of life on September 11th. This prevents the workflows from using an unsupported version of Node.js as well as deprecation warnings getting printed in the workflow logs. For more information please refer to https://github.com/actions/setup-node/releases/tag/v4.0.0 and actions/setup-node#850.
This major version mainly involves not using Node.js 16 internally anymore, which will be end of life on September 11th. This prevents the workflows from using an unsupported version of Node.js as well as deprecation warnings getting printed in the workflow logs. For more information please refer to https://github.com/actions/setup-node/releases/tag/v4.0.0 and actions/setup-node#850.
Hello everyone. The new version with support of node20 was released in v4.0.0. For now I'm going to close the issue. |
You need to change |
yes I just did that. Thanks |
Node16 will be deprecated on 09/11/2023 (link).
Node 16 is used by the action at the moment according to the source code:
setup-node/action.yml
Lines 35 to 36 in 5e21ff4
Is there a plan to release a node version update soon?
The text was updated successfully, but these errors were encountered: