-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
[Feature] Upgrade to Node 20 #149
Comments
Hi @leondz, |
It's been about 15 weeks. Any news? |
Node has been upgarded with the latest release. I apologise for a LONG delay. Please update the version of |
Great, thank you!! 😊 |
Great catch! |
Thanks! |
- 2.5.0 which uses node 20 vs node 16 Ref: contributor-assistant/github-action#149 Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
- 2.5.1 which uses node 20 vs node 16 Ref: contributor-assistant/github-action#149 Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
- 2.5.1 which uses node 20 vs node Ref: contributor-assistant/github-action#149 Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
Is your feature request related to a problem? Please describe.
contributor-assistant uses a deprecated version of Node (see https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/)
Describe the solution you'd like
Would like contributor-assistant to use Node 20
The text was updated successfully, but these errors were encountered: