-
Notifications
You must be signed in to change notification settings - Fork 198
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
update to node 16 #158
update to node 16 #158
Conversation
27013a6
to
832a805
Compare
@svasek While upgrading to node 16 I encountered an issue with the |
Hi @crazy-max,
|
@svasek Thanks for your feedback! That's what I thought. I will take a look and keep you in touch. |
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
@svasek Can you try again? Thx! |
Hi @crazy-max,
Thank you, |
Thanks again! |
Hi!
I guess it's related to this PR, but do I have to change something on my side? Thanks for your help, |
@jguillon This is not officially supported by GitHub. Suggest to open an issue on the |
Noted. For those who need to bypass the issue; simply |
Node 12 has an end of life on April 30, 2022.
https://github.blog/changelog/2021-12-10-github-actions-github-hosted-runners-now-run-node-js-16-by-default/
Signed-off-by: CrazyMax crazy-max@users.noreply.github.com