chore: migrate project from Node 16 to Node v22.22.1#1215
Open
sudorishabh wants to merge 1 commit intoRocketChat:developfrom
Open
chore: migrate project from Node 16 to Node v22.22.1#1215sudorishabh wants to merge 1 commit intoRocketChat:developfrom
sudorishabh wants to merge 1 commit intoRocketChat:developfrom
Conversation
- Update .nvmrc and README.md to specify Node v22.22.1 - Modify GitHub Action workflows to use Node v22.22.1 - Update @types/node in sub-packages for Node 22 support
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This Pull Request migrates the core development and CI/CD environments from Node.js v16.19.0 (which is now End-of-Life) to Node.js v22.22.1. This upgrade enables the use of modern Node APIs (such as native global fetch), improves security by adhering to an actively maintained LTS release, and ensures compatibility with modern tooling.
How Has This Been Tested?
Fixes #1214
Technical Changes
Node v16 vs v22
Why v22?
I picked Node 22 because it’s more stable and reliable right now, so there’s less chance of things breaking compared to Node 24.
Video/Screenshots
PR Test Details
Note: The PR will be ready for live testing at https://rocketchat.github.io/EmbeddedChat/pulls/pr-1214 after approval. Contributors are requested to replace
<pr_number>with the actual PR number.