chore: Upgrade Node.js to 22 and update dependencies #1509
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 PR introduces updates to the project's development and CI environment to ensure it remains modern, secure, and aligned with current best practices. This is a maintenance release with no changes to the library's public API or functionality.
The key changes include:
18
to the latest LTS version,22
. This ensures we are using a supported and performant version of Node.js for our builds, tests, and releases.actions/checkout
,actions/setup-node
, andactions/github-script
.npm update
. This addresses potential security vulnerabilities in older packages and keeps our dependencies current. Notable updates includesuperagent
,jsdoc
,mocha
, andmocha-junit-reporter
.There are no changes to endpoints, classes, or public methods. This update is focused solely on developer tooling and dependencies.
References
This change is part of routine maintenance to keep the project's dependencies and development environment up-to-date.
Testing
The primary method for testing these changes is to ensure that the entire CI pipeline, including all unit and integration tests, passes successfully with the updated Node.js version and dependencies. Reviewers should verify that all CI checks are green. No new test coverage is required as no new functionality has been added.
Checklist