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

Upgrade action to use node20 #1260

Closed
erikburt opened this issue Oct 13, 2023 · 3 comments · May be fixed by #1231
Closed

Upgrade action to use node20 #1260

erikburt opened this issue Oct 13, 2023 · 3 comments · May be fixed by #1231

Comments

@erikburt
Copy link

erikburt commented Oct 13, 2023

https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

Node 16 has reached its end of life, prompting us to initiate its deprecation process for GitHub Actions. Our plan is to transition all actions to run on Node 20 by Spring 2024. We will actively monitor the migration's progress and gather community feedback before finalizing the transition date. Starting October 23rd, workflows containing actions running on Node 16 will display a warning to alert users about the upcoming migration.

What you need to do

For Actions maintainers

Modify your actions to run on Node 20 instead of Node 16. For guidance, refer to the Actions configuration settings .


Note: also applies to nested restore action.

@MikeMcC399
Copy link

I'm now seeing GitHub warnings for this, for instance:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pnpm/action-setup@v2, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

@Piedone
Copy link

Piedone commented Jan 24, 2024

This is actually done, the action uses node20 now.

@erikburt
Copy link
Author

Closing ^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants