Skip to content
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

Merged
merged 4 commits into from
Feb 20, 2021
Merged

Conversation

kgabryje
Copy link
Member

@kgabryje kgabryje commented Feb 18, 2021

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

  • Has associated issue:
  • Changes UI
  • Requires DB Migration.
  • Confirm DB Migration upgrade and downgrade tested.
  • Introduces new feature or API
  • Removes existing feature or API

CC @villebro @rusackas @ktmud

@codecov-io
Copy link

codecov-io commented Feb 18, 2021

Codecov Report

Merging #13215 (7ce8d26) into master (2ce7982) will increase coverage by 5.41%.
The diff coverage is 68.49%.

Impacted file tree graph

@@            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     
Flag Coverage Δ
cypress 58.48% <68.49%> (+5.41%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...erset-frontend/src/SqlLab/components/ResultSet.tsx 4.16% <0.00%> (-0.09%) ⬇️
...end/src/SqlLab/components/RunQueryActionButton.tsx 52.77% <ø> (ø)
superset-frontend/src/chart/ChartContainer.jsx 100.00% <ø> (ø)
superset-frontend/src/chart/ChartRenderer.jsx 75.67% <0.00%> (-1.04%) ⬇️
...perset-frontend/src/common/components/Dropdown.tsx 50.00% <ø> (ø)
...t-frontend/src/common/components/Tooltip/index.tsx 100.00% <ø> (ø)
...perset-frontend/src/components/AlteredSliceTag.jsx 92.00% <ø> (ø)
superset-frontend/src/components/CachedLabel.jsx 42.10% <ø> (ø)
...ontend/src/components/CertifiedIconWithTooltip.tsx 0.00% <ø> (ø)
...perset-frontend/src/components/CopyToClipboard.jsx 57.14% <0.00%> (ø)
... and 164 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2ff8741...7ce8d26. Read the comment docs.

Copy link
Member

@villebro villebro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kgabryje
Copy link
Member Author

Super excited about this! 🎉 We also probably need to bump it in these places:

Oops, my bad. Done

@ktmud
Copy link
Member

ktmud commented Feb 18, 2021

Can we stick with current LTS version v14 instead?

@villebro
Copy link
Member

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.

@ktmud
Copy link
Member

ktmud commented Feb 19, 2021

Yeah, they specifically recommend Production applications should only use Active LTS or Maintenance LTS releases.

We are unlikely to use any cutting-edge features from the current release anyway, so it's probably safer to go with LTS.

@etr2460
Copy link
Member

etr2460 commented Feb 19, 2021

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

Copy link
Member

@villebro villebro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review comments @ktmud and @etr2460 ; @kgabryje would you mind downgrading to v14 to address the feedback?

@kgabryje
Copy link
Member Author

@villebro Done! Thank you for feedback @ktmud @etr2460

@ktmud ktmud changed the title chore: Bump node version to v15.8.0 chore: build node.js to v14 Feb 20, 2021
Copy link
Member

@ktmud ktmud left a 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.

@kgabryje
Copy link
Member Author

@ktmud Done

@villebro villebro changed the title chore: build node.js to v14 chore: bump node.js to v14 Feb 20, 2021
@villebro villebro merged commit 19a6043 into apache:master Feb 20, 2021
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 1.2.0 labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/XS 🚢 1.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants