Skip to content

chore: upgrade Node.js to v22 and update dependencies#468

Open
vaibhavchopra-wq wants to merge 1 commit into
masterfrom
chore/node-version-upgrade
Open

chore: upgrade Node.js to v22 and update dependencies#468
vaibhavchopra-wq wants to merge 1 commit into
masterfrom
chore/node-version-upgrade

Conversation

@vaibhavchopra-wq
Copy link
Copy Markdown

@vaibhavchopra-wq vaibhavchopra-wq commented Apr 22, 2026

  • Update Node.js version from EOL versions (12/14/16) to v22
  • Migrate Babel 6 to Babel 7 (@babel/cli, @babel/core, @babel/preset-env)
  • Update .babelrc to target Node 22
  • Update GitHub Actions to use actions/checkout@v4 and actions/setup-node@v4
  • Upgrade dev dependencies (mocha 11, chai 5, nock 14, nyc 17)
  • Upgrade axios to 1.7.0
  • Add engines field requiring Node >= 22.0.0
  • Rebuild dist/ to sync with lib/ (adds missing compiled files)
  • Reduces npm audit vulnerabilities from 55 to 3

Note :- Please follow the below points while attaching test cases document link below:

- If label Tested is added then test cases document URL is mandatory.

- Link added should be a valid URL and accessible throughout the org.

- If the branch name contains hotfix / revert by default the BVT workflow check will pass.

Test Case Document URL
https://docs.google.com/document/d/1RA9GcYqNGnUcQjIYAF0jxBa-DYw_iHRqMMMe-t_c3IE/edit?usp=sharing

- Update Node.js version from EOL versions (12/14/16) to v22
- Migrate Babel 6 to Babel 7 (@babel/cli, @babel/core, @babel/preset-env)
- Update .babelrc to target Node 22
- Update GitHub Actions to use actions/checkout@v4 and actions/setup-node@v4
- Upgrade dev dependencies (mocha 11, chai 5, nock 14, nyc 17)
- Upgrade axios to 1.7.0
- Add engines field requiring Node >= 22.0.0
- Rebuild dist/ to sync with lib/ (adds missing compiled files)
- Reduces npm audit vulnerabilities from 55 to 3
@vaibhavchopra-wq vaibhavchopra-wq marked this pull request as ready for review April 29, 2026 10:22
@vaibhavchopra-wq
Copy link
Copy Markdown
Author

@arpitbbhayani let me know if we plan to keep dist files in the repo, they were not updated after the last few releases, so more files in the diff

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant