Skip to content

chore: use new mongodb-client-encryption and update filter to support versions #4132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 5, 2024

Conversation

baileympearson
Copy link
Contributor

@baileympearson baileympearson commented Jun 5, 2024

Description

What is changing?

Is there new documentation needed for these changes?

What is the motivation for this change?

going forward, we'll have FLE tests that make use of newer libmongocrypt features. We haven't had this issue in the past, because we've always tested with latest mongodb-client-encryption, but now that we ensure compatibility between [email protected] and latest driver, we'll need to start skipping tests on versions of our bindings that don't support the features under test.

Double check the following

  • Ran npm run check:lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

@nbbeeken nbbeeken self-assigned this Jun 5, 2024
@nbbeeken nbbeeken added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label Jun 5, 2024
@nbbeeken nbbeeken merged commit 65c9267 into mongodb:main Jun 5, 2024
24 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Primary Review In Review with primary reviewer, not yet ready for team's eyes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants