-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
drop support for node 12 #11210
drop support for node 12 #11210
Conversation
8c6fad5
to
5c7edfa
Compare
Related: #11198 |
9eedce5
to
5bce35c
Compare
Turns out Node 18.x requires a glibc version greater than what's available on Ubuntu 18.04. |
a2bdfe0
to
7322adb
Compare
We can probably close #10013 thanks to the changes. |
da46468
to
aeb9ab2
Compare
Turns out Node 18.x uses I now explicitly set the default hostname to |
850c018
to
5b138c2
Compare
I dropped trying to test on Node 18, it will require more investigation to get working. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 The build and tests pass successfully.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me as well 👍
Keep supporting Node 14.x but recommend Node 16.x.
5b138c2
to
2cc3fcf
Compare
Keep supporting Node 14.x but recommend Node 16.x.
Closes #10013
How to test
Nothing should have changed. Everything should work like before with Node 14 or Node 16.
Review checklist
Reminder for reviewers