-
-
Notifications
You must be signed in to change notification settings - Fork 43
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 the runner to use Nodejs 16 #459
Comments
I already created PR for that #456 |
Bump. Sure would be nice if this were merged. |
Hey any update on the node 16 bump? I noticed the PR mentioned above has been closed and never merged! Cheers |
Re: updates on the node 16 bump? @ricardodantas. |
Same here just now. Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions-ecosystem/[email protected]. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. |
is this action still maintained? this will start failing on June 1st |
I just replaced the action with the below code
|
@micnncim I see your "busy" tag, but please take action on this. My workflows are 2 day from doom, and I need time to change versions after you release v2 or other next tag |
That action seems to be unmaintained and causes warnings (actions-ecosystem/action-add-labels#459). Let's just use the API directly, like we already do in `.github/workflows/labels-from-comments.yml`
That action seems to be unmaintained and causes warnings (actions-ecosystem/action-add-labels#459). Let's just use the API directly, like we already do in `.github/workflows/labels-from-comments.yml`
This repo is probably abandoned so easier to just use
After all not everything needs to be an action. Note Yeah it needs to be |
What you want to add
Upgrade runner to use Nodejs 16.
Why this is needed
Because the Nodejs 14 runner will get deprecated soon.
The text was updated successfully, but these errors were encountered: