-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
Use Case
Node25 has been released; now `latest` tasks in CI test against Node25 and we no longer test against Node24.
User Experience
- What is the desired/expected outcome for the user once this ticket is implemented?
- If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Is there an opportunity for better cross-driver alignment or testing in this area?
- Is there an opportunity to improve existing documentation on this subject?
Acceptance Criteria
Implementation Requirements
- Add node24 to CI in all repositories
- bson
zstd(already completed)- mongodb-client-encryption
- kerberos
- driver
- mongodb-connection-string-url
- Ensure the `latest` tasks continue to test on Node25
Testing Requirements
- All tests pass
- If any failures are encountered and are non-trivial to fix, file a follow up ticket in the Node24 support epic.
Documentation Requirements
- n/a
Follow Up Requirements
- n/a
1.
|
Add Node 24 to CI in BSON | NODE-7281 |
|
Needs Verification | Durran Jordan | |
2.
|
Add Node 24 to CI in mongodb-client-encryption | NODE-7282 |
|
Needs Verification | Durran Jordan | |
3.
|
Add Node 24 to CI in driver | NODE-7283 |
|
Ready for Work | Unassigned | |
4.
|
Add Node 24 to CI in mongodb-connection-string-url | NODE-7284 |
|
In Progress | Sergey Zelenov | |
5.
|
Add Node 24 to CI in kerberos | NODE-7285 |
|
Needs Verification | Durran Jordan |