fix(deps): update dependency mongodb to v6 #351
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.17.2
->6.10.0
Release Notes
mongodb/node-mongodb-native (mongodb)
v6.10.0
Compare Source
Features
Bug Fixes
v6.9.0
Compare Source
Features
mongocryptdSpawnPath
andmongocryptdSpawnArgs
(#4151) (f48f8d3)allowPartialTrustChain
TLS flag (#4228) (d6c147d)Bug Fixes
error.writeConcern.code
to determine retryability (#4155) (b26c328)Performance Improvements
v6.8.2
Compare Source
The MongoDB Node.js team is pleased to announce version 6.8.2 of the
mongodb
package!Release Notes
Fixed mixed use of cursor.next() and cursor[Symbol.asyncIterator]
In 6.8.0, we inadvertently prevented the use of cursor.next() along with using for await syntax to iterate cursors. If your code made use of the following pattern and the call to cursor.next retrieved all your documents in the first batch, then the for-await loop would never be entered. This issue is now fixed.
Bug Fixes
Documentation
We invite you to try the
mongodb
library immediately, and report any issues to the NODE project.v6.8.1
Compare Source
v6.8.0
Compare Source
Features
Bug Fixes
Binary
as local KMS provider key (#4160) (fb724eb)v6.7.0
Compare Source
Features
Bug Fixes
v6.6.2
Compare Source
Bug Fixes
v6.6.1
Compare Source
Bug Fixes
v6.6.0
Compare Source
The MongoDB Node.js team is pleased to announce version 6.6.0 of the
mongodb
package!Release Notes
Aggregation pipelines can now add stages manually
When creating an aggregation pipeline cursor, a new generic method
addStage()
has been added in the fluid API for users to add aggregation pipeline stages in a general manner.Thank you @prenaissance for contributing this feature!
cause and package name included for
MongoMissingDependencyErrors
MongoMissingDependencyError
s now include acause
and adependencyName
field, which can be used to programmatically determine which package is missing and why the driver failed to load it.For example:
ServerDescription
Round Trip Time (RTT) measurement changes(1)
ServerDescription.roundTripTime
is now a moving averagePreviously,
ServerDescription.roundTripTime
was calculated as a weighted average of the most recently observed heartbeat duration and the previous duration. This update changes this behaviour to averageServerDescription.roundTripTime
over the last 10 observed heartbeats. This should reduce the likelihood that the selected server changes as a result of momentary spikes in server latency.(2) Added
minRoundTripTime
toServerDescription
A new
minRoundTripTime
property is now available on theServerDescription
class which gives the minimum RTT over the last 10 heartbeats. Note that this value will be reported as 0 when fewer than 2 samples have been observed.type
supported inSearchIndexDescription
It is now possible to specify the type of a search index when creating a search index:
Collection.findOneAndModify
'sUpdateFilter.$currentDate
no longer throws on collections with limited schemaExample:
TopologyDescription
now properly stringifies itself to JSONThe
TopologyDescription
class is exposed by the driver in server selection errors and topology monitoring events to provide insight into the driver's current representation of the server's topology and to aid in debugging. However, the TopologyDescription usesMap
s internally, which get serialized to{}
when JSON stringified. We recommend using Node'sutil.inspect()
helper to print topology descriptions becauseinspect
properly handles all JS types and all types we use in the driver. However, if JSON must be used, theTopologyDescription
now provides a customtoJSON()
hook:Omit
readConcern
andwriteConcern
inCollection.listSearchIndexes
options argumentThis type change is a correctness fix.
Collection.listSearchIndexes
is an Atlas specific method, and Atlas' search indexes do not supportreadConcern
andwriteConcern
options. The types for this function now reflect this functionality.Don't throw error when non-read operation in a transaction has a
ReadPreferenceMode
other than'primary'
The following error will now only be thrown when a user provides a
ReadPreferenceMode
other thanprimary
and then tries to perform a command that involves a read:Prior to this change, the Node Driver would incorrectly throw this error even when the operation does not perform a read.
Note: a
RunCommandOperation
is treated as a read operation for this error.TopologyDescription.error
type isMongoError
This type change is a correctness fix.
Before this change, the following errors that were not instances of
MongoServerError
were already passed intoTopologyDescription.error
at runtime:MongoNetworkError
(excludingMongoNetworkRuntimeError
)MongoError
with aMongoErrorLabel.HandshakeError
labelindexExists()
no longer supports thefull
optionThe
Collection.indexExists()
helper supported an option,full
, that modified the internals of the method. Whenfull
was set totrue
, the driver would always returnfalse
, regardless of whether or not the index exists.The
full
option is intended to modify the return type of index enumeration APIs (Collection.indexes()
andCollection.indexInformation()
, but since the return type ofCollection.indexExists()
this option does not make sense for theCollection.indexExists()
helper.We have removed support for this option.
indexExists()
,indexes()
andindexInformation()
support cursor options in TypescriptThese APIs have supported cursor options at runtime since the 4.x version of the driver, but our Typescript has incorrectly omitted cursor options from these APIs.
Index information helpers have accurate Typescript return types
Collection.indexInformation()
,Collection.indexes()
andDb.indexInformation()
are helpers that return index information for a given collection or database. These helpers take an option,full
, that configures whether the return value contains full index descriptions or a compact summary:However, the Typescript return type of these helpers was always
Document
. Thanks to @prenaissance, these helpers now have accurate type information! The helpers return a new type,IndexDescriptionCompact | IndexDescriptionInfo[]
, which accurately reflects the return type of these helpers. The helpers also support type narrowing by providing a boolean literal as an option to the API:AWS credentials with expirations no longer throw when using on-demand AWS KMS credentials
In addition to letting users provide KMS credentials manually, client-side encryption supports fetching AWS KMS credentials on-demand using the AWS SDK. However, AWS credential mechanisms that returned access keys with expiration timestamps caused the driver to throw an error.
The driver will no longer throw an error when receiving an expiration token from the AWS SDK.
ClusterTime
interfacesignature
optionalityThe
ClusterTime
interface incorrectly reported thesignature
field as required, the server may omit it, so the typescript has been updated to reflect reality.Summary
Features
timeoutMS
anddefaultTimeoutMS
(#4068) (ddd1e81)cause
and package name for allMongoMissingDependencyError
s (#4067) (62ea94b)minRoundTripTime
toServerDescription
and changeroundTripTime
to a moving average (#4059) (0e3d6ea)type
option in create search index helpers (#4060) (3598c23)bson
to ^6.5.0 (#4035) (8ab2055)bson
to ^6.7.0 (#4099) (7f191cf)Bug Fixes
Collection.findOneAndModify
UpdateFilter.$currentDate
(#4047) (a8670a7)ReadPreferenceMode
other thanprimary
(#4075) (39fc198)v
tocreateIndexes
command whenversion
is specified (#4043) (1879a04)TopologyDescription.error
type toMongoError
(#4028) (30432e8)full
is set totrue
(#4034) (0ebc1ac)libmongocrypt
after fetching AWS KMS credentials (#4057) (c604e74)ClusterTime.signature
can be undefined (#4069) (ce55ca9)Performance Improvements
setTimeout
callback (#4094) (6abc074)Documentation
We invite you to try the
mongodb
library immediately, and report any issues to the NODE project.v6.5.0
Compare Source
Features
Bug Fixes
CERT_HAS_EXPIRED
(#4014) (057c223)Connection
class (#4022) (69de253)Performance Improvements
v6.4.0
Compare Source
Features
^6.3.0
(#3983) (9401d09)Bug Fixes
Performance Improvements
v6.3.0
Compare Source
Features
Bug Fixes
v6.2.0
Compare Source
Features
awaited
field to SDAM heartbeat events (#3895) (b50aadc)Bug Fixes
v6.1.0
Compare Source
Features
Bug Fixes
v6.0.0
Compare Source
⚠ BREAKING CHANGES
onKMSProvidersRefresh
(#3787)Features
mongodb-js/saslprep
as a required dependency (#3815) (bd031fc)onKMSProvidersRefresh
(#3787) (844aa52)Bug Fixes
v5.9.2
Compare Source
The MongoDB Node.js team is pleased to announce version 5.9.2 of the
mongodb
package!Release Notes
Fix connection leak when serverApi is enabled
When enabling serverApi the driver's RTT mesurment logic (used to determine the closest node) still sent the legacy hello command "isMaster" causing the server to return an error. Unfortunately, the error handling logic did not correctly destroy the socket which would cause a leak.
Both sending the correct hello command and the error handling connection clean up logic are fixed in this change.
Bug Fixes
Documentation
We invite you to try the
mongodb
library immediately, and report any issues to the NODE project.v5.9.1
Compare Source
The MongoDB Node.js team is pleased to announce version 5.9.1 of the
mongodb
package!Release Notes
insertedIds
in bulk write now contain only successful insertionsPrior to this fix, the bulk write error's
result.insertedIds
property contained the_id
of each attempted insert in a bulk operation.Now, when a
bulkwrite()
or aninsertMany()
operation rejects one or more inserts, throwing an error, the error'sresult.insertedIds
property will only contain the_id
fields of successfully inserted documents.Fixed edge case leak in
findOne()
When running a
findOne
against a time series collection, the driver left the implicit session for the cursor un-ended due to the way the server returns the resulting cursor information. Now the cursor will always be cleaned up regardless of the outcome of the find operation.Bug Fixes