-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
chore: bump node.js to v14 #13215
chore: bump node.js to v14 #13215
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13215 +/- ##
==========================================
+ Coverage 53.06% 58.48% +5.41%
==========================================
Files 489 468 -21
Lines 17314 15942 -1372
Branches 4482 4108 -374
==========================================
+ Hits 9187 9323 +136
+ Misses 8127 6619 -1508
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
Super excited about this! 🎉 We also probably need to bump it in these places:
Oops, my bad. Done |
Can we stick with current LTS version v14 instead? |
I personally prefer keeping these as recent as possible so we can incrementally add support for new features, but If there are concerns that going with v15 will introduce stability issues, I vote going with v14. When reading https://nodejs.org/en/about/releases/ I get the impression that only library developers should go with Current and all others should use LTS. So perhaps v14 is safer. |
Yeah, they specifically recommend We are unlikely to use any cutting-edge features from the current release anyway, so it's probably safer to go with LTS. |
I completely agree with Jesse here, generally Node odd numbered releases are full of bugs/issues. I'd feel much better with keeping us at 14 |
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.
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. Do you mind updating superset-frontend/.nvmrc
as well? I know probably not many people use it, but we do recommend nvm use
in CONTRIBUTING.md.
@ktmud Done |
SUMMARY
Bumps node version to v15.8.0 - current stable. Changelog: https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V15.md
Docker image: https://hub.docker.com/layers/node/library/node/15/images/sha256-05b68ed85be74950052b3afe25ce93b9f534d86454cb12547964739c607557b1?context=explore
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TEST PLAN
ADDITIONAL INFORMATION
CC @villebro @rusackas @ktmud