-
Notifications
You must be signed in to change notification settings - Fork 36
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 Node.js 16 #484
Comments
Co-authored-by: James Hegedus <jthegedus@hey.com> Fixes #484
Hi all, sorry for the delay here. We have merged the PR #488 which resolved these issues. As far as releasing this specific change goes, I want to re-jig the GitHub Releases to follow the automation we have in our other repos, so until a tagged version becomes available, I will ask you all to use the commit reference style:
Where the SHA is the commit from master after the merge. NOTE: an update to the min version of Node is considered a breaking API change to the Action, so this will release under tag |
@jthegedus, it might be worth either creating issue(s) for the changes to the release process so that others can help if they are able or manually releasing this change. GitHub announced their intention to migrate Node.js 12 actions to Node.js 16 around June-August 2023, which could potentially be needlessly disruptive if all doesn't go smoothly for everyone. |
@Kurt-von-Laven As part of my upcoming updates to this repo the release process will follow the same as the core asdf repo so any core member can release with a simple PR merge. Updating this repo is top of my priority list, so when I get a chance in the coming weeks this will be addressed. |
Thank you! It's greatly appreciated. |
Co-authored-by: James Hegedus <jthegedus@hey.com> Fixes asdf-vm#484
This repository uses Node.js 12 actions, which are deprecated. GitHub Actions recently began adding the following annotation warning all users of asdf-vm/actions:
The text was updated successfully, but these errors were encountered: