-
Notifications
You must be signed in to change notification settings - Fork 33
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
Replace Node.js 16 with Node.js 20 #144
Conversation
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
Thank you 😊 |
👋 I'm curious why this needed to be a new major version release? |
👋 @andyw8 I might have been a bit too conservative on the versioning. As it seems that all the action runners provided by GitHub now supports Node.js 20, we could probably have gotten away with simply a patch version. Though, it is technically a breaking change. At least for self-hosted runners. However, one could debate if it is the responsibility of the action or the self-hosted users to avoid environment-related breaking changes. |
see andstor/file-existence-action#144 Signed-off-by: Cyberczy <109653523+Cyberczy@users.noreply.github.com>
see andstor/file-existence-action#144 Signed-off-by: Cyberczy <109653523+Cyberczy@users.noreply.github.com>
Closes #143
According to GitHub Actions migration guide, this is the only step that we need to take to move from Node.js 16 to Node.js 20
https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#example-using-nodejs-v20
On top I have updated deprecated dependencies