Skip to content
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

Closed
kinano opened this issue Sep 6, 2023 · 8 comments
Closed

Node 16 deprecation #850

kinano opened this issue Sep 6, 2023 · 8 comments
Assignees
Labels
feature request New feature or request to improve the current logic needs eyes

Comments

@kinano
Copy link

kinano commented Sep 6, 2023

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

runs:
using: 'node16'

Is there a plan to release a node version update soon?

@kinano kinano added feature request New feature or request to improve the current logic needs triage labels Sep 6, 2023
@dusan-trickovic
Copy link

Hello, @kinano! Thank you for creating an issue, we'll look into this :)

@MikeMcC399
Copy link

@dusan-trickovic

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 node16 deprecation notices to be generated starting on October 23, 2023.

So apart from the fact the Node.js 16 is already in end-of-life status, it will soon start to visibly affect GitHub Action workflows using actions/setup-node if no steps are taken to provide an updated release running on node20.

Please release a new version supporting node20 as requested by @kinano!

@dusan-trickovic
Copy link

Hello @MikeMcC399! Thank you very much for your input, we are looking into this :)

@MikeMcC399

This comment was marked as outdated.

@MikeMcC399
Copy link

MikeMcC399 commented Oct 23, 2023

timvandermeij added a commit to timvandermeij/pdf.js that referenced this issue Oct 28, 2023
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.
timvandermeij added a commit to timvandermeij/pdf.js that referenced this issue Oct 28, 2023
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.
@dmitry-shibanov dmitry-shibanov self-assigned this Dec 25, 2023
@dmitry-shibanov
Copy link
Contributor

Hello everyone. The new version with support of node20 was released in v4.0.0. For now I'm going to close the issue.

@MikeMcC399
Copy link

@rwader-swi

You need to change actions/setup-node@v3 to actions/setup-node@v4 in your workflow.

@rwader-swi
Copy link

@rwader-swi

You need to change actions/setup-node@v3 to actions/setup-node@v4 in your workflow.

yes I just did that. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request to improve the current logic needs eyes
Projects
None yet
Development

No branches or pull requests

5 participants