-
Notifications
You must be signed in to change notification settings - Fork 5
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
Node12 is deprecated #4
Comments
Hi @WtfJoke, thanks for the issue, think I will go for Node18, just to be a bit more future proof :) Will fix it later today |
Closed by #6 and available in v3 |
Thank you! |
Thanks for the new release! 🥳 Btw, seems like it's still |
Since node16 is now eol, just wanted to let you know, you can use node20 now :) See actions/runner#2619 (comment) There seems to be however no official anouncement/docs update yet |
Thanks I will try to update to node20, it failed last time 👯 |
It is now done, also updated v3 to point to v3.0.1 |
Awesome, thank you |
Hello @mbogh, Thanks for creating this action! The v3 and v3.0.1 still point to d48191d with node16. I am currently using: |
Added a new v3.0.2 and update v3 to point to same hash |
Hey @mbogh
Thank you for creating this action :)
The action currently still runs on node12. Node12 is eol and soon Node16.
Would be great if you can release a node16 version.
EDIT: Will be fixed with #3
The text was updated successfully, but these errors were encountered: