Skip to content

feat!: upgrade project's Node version to v22#37223

Open
hainenber wants to merge 1 commit intomasterfrom
feat/bump-node-to-v22
Open

feat!: upgrade project's Node version to v22#37223
hainenber wants to merge 1 commit intomasterfrom
feat/bump-node-to-v22

Conversation

@hainenber
Copy link
Contributor

feat!: upgrade project's Node version to v22

SUMMARY

Node 20 is about to EoL in upcoming 3 months so IMO, we should proactively bump to next LTS, which is 22. There aren't any noticeable breaking changes between these LTS versions so I'd say we're pretty good to go

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A

TESTING INSTRUCTIONS

Green CI for acceptance criterion

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

Signed-off-by: hainenber <dotronghai96@gmail.com>
@codeant-ai-for-open-source
Copy link
Contributor

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@github-actions github-actions bot added doc Namespace | Anything related to documentation embedded dependencies:npm labels Jan 17, 2026
@hainenber hainenber requested a review from villebro January 17, 2026 14:35
@dosubot dosubot bot added the risk:breaking-change Issues or PRs that will introduce breaking changes label Jan 17, 2026
@netlify
Copy link

netlify bot commented Jan 17, 2026

Deploy Preview for superset-docs-preview ready!

Name Link
🔨 Latest commit e6031a6
🔍 Latest deploy log https://app.netlify.com/projects/superset-docs-preview/deploys/696b9e34e62ceb000863f03c
😎 Deploy Preview https://deploy-preview-37223--superset-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@codeant-ai-for-open-source
Copy link
Contributor

CodeAnt AI finished reviewing your PR.

Copy link
Contributor

@bito-code-review bito-code-review bot left a comment

Choose a reason for hiding this comment

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

Code Review Agent Run #aa8f23

Actionable Suggestions - 1
  • superset-websocket/.nvmrc - 1
Review Details
  • Files reviewed - 5 · Commit Range: e6031a6..e6031a6
    • docs/.nvmrc
    • superset-embedded-sdk/.nvmrc
    • superset-frontend/.nvmrc
    • superset-websocket/.nvmrc
    • superset-websocket/utils/client-ws-app/.nvmrc
  • Files skipped - 2
    • superset-frontend/package-lock.json - Reason: Filter setting
    • superset-frontend/package.json - Reason: Filter setting
  • Tools
    • Whispers (Secret Scanner) - ✔︎ Successful
    • Detect-secrets (Secret Scanner) - ✔︎ Successful

Bito Usage Guide

Commands

Type the following command in the pull request comment and save the comment.

  • /review - Manually triggers a full AI review.

  • /pause - Pauses automatic reviews on this pull request.

  • /resume - Resumes automatic reviews.

  • /resolve - Marks all Bito-posted review comments as resolved.

  • /abort - Cancels all in-progress reviews.

Refer to the documentation for additional commands.

Configuration

This repository uses Superset You can customize the agent settings here or contact your Bito workspace admin at evan@preset.io.

Documentation & Help

AI Code Review powered by Bito Logo

@@ -1 +1 @@
v20.18.3
v22.22.0
Copy link
Contributor

Choose a reason for hiding this comment

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

Version Mismatch

The .nvmrc specifies Node.js v22.22.0, but the package.json engines require '^20.19.4', creating an inconsistency that could cause issues with package managers or CI if engines are enforced.

Code Review Run #aa8f23


Should Bito avoid suggestions like this for future reviews? (Manage Rules)

  • Yes, avoid them

Copy link
Member

Choose a reason for hiding this comment

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

@hainenber I do remember having to update this in a few random places last time I did it (a long time ago!)

Copy link
Member

Choose a reason for hiding this comment

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

I wonder if there's some good way to centralize all of this to make it easier.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, to centralize Node.js version management in this monorepo, consider placing a single .nvmrc at the root. This lets all subprojects inherit the version. Alternatively, use Volta by adding a 'volta' field in the root package.json specifying the node version.

.nvmrc

v22.22.0

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We can have a centralized .nvmrc in root dir /superset and sym-link this particular file to other sub-projects. Wdyt?

Copy link
Contributor

Choose a reason for hiding this comment

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

Centralizing the .nvmrc at the root and sym-linking to sub-projects is a solid idea—it reduces duplication and simplifies updates across the monorepo. Just ensure sym-links are handled properly in CI/CD and version control to avoid issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies:npm doc Namespace | Anything related to documentation embedded risk:breaking-change Issues or PRs that will introduce breaking changes size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants