1.6.1 release

Fixed

• Fix libbson dependency in pkg-config for PPA.

node-v2.2.1

The MongoDB Node.js team is pleased to announce version 2.2.1 of the mongodb-client-encryption package!

Release Highlights

This is a bug fix release by upgrading libmongocrypt to 1.6.0.

Bug Fixes

• Use correct schema when collMod command includes validator.$jsonSchema.

We invite you to try the mongodb-client-encryption library immediately, and report any issues to the NODE project.

1.6.0 release

New Features

• Support accessToken to authenticate with Azure.

Fixed

• Use correct schema when collMod command includes validator.$jsonSchema.

node-v2.2.0

The MongoDB Node.js team is pleased to announce version 2.2.0 of the mongodb-client-encryption package!

Release Highlights

Key Management API

Version 2.2.0 of mongodb-client-encryption includes support for the key management API. After this release, the ClientEncryption class can be used to perform
common key management operations. Please refer to the mongodb-client-encryption documentation for the ClientEncryption class for a full list of available key management methods and usage examples (available
here).

Issue Links

Features

• NODE-4241 add support for rewrapManyDataKey and keyMaterial (e2a7411)
• NODE-4394 add key management API to node bindings (e54db88)

Bug Fixes

• NODE-4242 do not run mongocryptd if bypassQueryAnalysis (f9d36e5)
• add missing import in Node.js bindings TS definitions (4b0240a)
• NODE-4251 fix markCommand deserialization (9b0cf44)
• NODE-4356 update rewrapManyDataKey to use UpdateOne bulk ops (590a96b)
• NODE-4260 mongocrypterror has name getter (74b6ccb)

We invite you to try the mongodb-client-encryption library immediately, and report any issues to the NODE project.

1.6.0-alpha0

New Features

• Support accessToken to authenticate with GCP.

Improvements

• Use CRLF, not LF, for HTTP request newlines.
• Include full body of HTTP errors in mongocrypt_status_t.

1.5.2 release

ChangeLog

1.5.2

Fixed

Fix a potential data corruption bug in RewrapManyDataKey when rotating encrypted data encryption keys backed by GCP or Azure key services.

The following conditions will trigger this bug:

• A GCP-backed or Azure-backed data encryption key being rewrapped requires fetching an access token for decryption of the data encryption key.

The result of this bug is that the key material for all data encryption keys being rewrapped is replaced by new randomly generated material, destroying the original key material.

To mitigate potential data corruption, upgrade to this version or higher before using RewrapManyDataKey to rotate Azure-backed or GCP-backed data encryption keys. A backup of the key vault collection should always be taken before key rotation.

node-v2.2.0-alpha.6

chore(release): 2.2.0-alpha.6

node-v2.2.0-alpha.5

chore(release): 2.2.0-alpha.5

1.5.1 release

Warnings

This release has a severe bug in the contexts returned by mongocrypt_ctx_rewrap_many_datakey_init that may result in data corruption. Please upgrade to 1.5.2 to use mongocrypt_ctx_rewrap_many_datakey_init.

New Features

• Update Java bindings to support remaining 1.5.0 API.

node-v2.2.0-alpha.4

The MongoDB Node.js team is pleased to announce version 2.2.0-alpha.4!

Release Highlights

Features

• Updates libmongocrypt to 1.5.0

Bug Fixes

• NODE-4339: Removes indexKeyId from encryption options
• NODE-4260: Fixes error when crypt errors during bulk write.