-
Notifications
You must be signed in to change notification settings - Fork 158
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 to node20 #64
Comments
@shallwefootball is there a chance this action will be compliant with the requirements or should we fork it instead and maintain it on our fork? Thanks in advance! |
GitHub will enforce Node20 on May 13 - is there a chance this gets updated by that time? |
+1 for upgrading to node20. |
@shallwefootball I also pushed PR 67 again from my fork. I went through the same process as in my earlier PR 46 |
Looks like we still have some time before the current version of the action will stop working: https://github.blog/changelog/2024-05-17-updated-dates-for-actions-runner-using-node20-instead-of-node16-by-default/ |
It's fixed now with this commit also there is a PR opened to update te dependencies. We need a new release to close this issue as not there is no way to use a fixed version as an action :( |
This action requires Node20 to comply to latest GitHub requirements:
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/
The text was updated successfully, but these errors were encountered: