- 
    Type:
Task
 - 
    Resolution: Fixed
 - 
    Priority:
Unknown
 - 
    Affects Version/s: None
 - 
    Component/s: None
 
Use Case
As a... (who is this for)
I want... (what is the desired change)
So that... (why is the change desired)
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
- Release zstd@2.0.0-alpha
 - Adjust the driver’s peer dependency on zstd to support 2.x versions of zstd
 - Update zstd’s platform matrix
 - Update the driver CI matrix to test against both zstd@1.0 and zstd@2.0
 - Once all driver tests pass, release zstd@2.0
 
Testing Requirements
- unit test, spec test sync, etc
 
Documentation Requirements
- DOCSP ticket, API docs, etc
 
Follow Up Requirements
- additional tickets to file, required releases, etc
 - if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward