-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
Use Case
As a Node.js user and driver developer
I want the latest LTS to be tested.
So that we're sure the latest version works as expected.
User Experience
- All Node.js users that use the LTS release branch.
Dependencies
- Node.js
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Nothing
- Is there an opportunity for better cross-driver alignment or testing in this area?
- No
- Is there an opportunity to improve existing documentation on this subject?
- Yes, compat tables need updating upon next release
Acceptance Criteria
Implementation Requirements
- Add Node.js 22 LTS to all supported library's matrices
- driver, bson, client encryption, legacy driver, kerberos, zstd, connection string, dbx-js-tools
- Double check any latest tasks are running with Node.js 23
Testing Requirements
- All tests pass on node 22
Documentation Requirements
- Inform the docs team on the next release that there are compat table changes for Node version
Follow Up Requirements
- None
1.
|
Add Node.js 22 LTS to CI matrix to node-mongodb-native | NODE-6557 | Needs Verification | Warren James | ||
2.
|
Add Node.js 22 LTS to CI matrix to dbx-js-tools | NODE-6559 | In Progress | Warren James | ||
3.
|
Add Node.js 22 LTS to CI matrix in kerberos repo | NODE-6561 | In Progress | Warren James |