Skip to content
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

feat(NODE-6307): use libmongocrypt 1.11.0 #38

Merged
merged 2 commits into from
Aug 5, 2024

Conversation

baileympearson
Copy link
Collaborator

@baileympearson baileympearson commented Aug 2, 2024

Description

What is changing?

Just waiting on https://spruce.mongodb.com/task/libmongocrypt_release_publish_upload_all_9a88ac5698e8e3ffcd6580b98c247f0126f26c40_24_08_01_18_30_17/logs?execution=0.

Is there new documentation needed for these changes?

What is the motivation for this change?

Release Highlight

Update bindings to use libmongocrypt 1.11.0

  • Support range algorithm as stable.

See the libmongocrypt release here

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

@baileympearson baileympearson marked this pull request as ready for review August 5, 2024 18:45
@baileympearson baileympearson changed the title feat: use libmongocrypt 1.11.0 feat(NODE-6307): use libmongocrypt 1.11.0 Aug 5, 2024
@nbbeeken nbbeeken self-assigned this Aug 5, 2024
@nbbeeken nbbeeken added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label Aug 5, 2024
@nbbeeken nbbeeken merged commit bc85202 into mongodb-js:main Aug 5, 2024
30 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