Use Case

As a... (who is this for)
I want... (what is the desired change)
So that... (why is the change desired)

User Impact

• What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• N/A

Unknowns

• questions that need to be answered to determine implementation

Acceptance Criteria

Implementation Requirements

• Identify all peer and peer optional dependencies for the following repos and branches:
  • node-mongodb-native (main, 5.x, 4.x)
  • js-bson (main, 5.x, 4.x)
  • libmongocrypt - node bindings (master)
  • kerberos (main)
  • zstd (main)
  • nodejs-mongodb-legacy (main)
• For each identified dependency
  • If the dependency is 3rd party, ensure there is a test in CI that tests the lowest patch-pinned version of each major version in the supported range (update the CI config to install the lowest version instead of relying on automatic semver parsing from package.json or a non-patch-specific npm install in a script)
  • If the dependency is ours, check whether there is a test in CI that tests the lowest patch-pinned version as well as one that tests the latest semver-compatible version for each major in the supported range; consult with the team on next steps if either or both of the above are missing for some dependency

Testing Requirements

• All existing tests should continue to pass
• Investigate any failures; skip the tests and file follow ups for any new bugs; test-only fixes are in scope for this work

Documentation Requirements

• N/A

Follow Up Requirements

• Files tickets for any actual bugs discovered