chore(main): release 6.6.0 [skip-ci] #4037
                
     Merged
            
            
          
  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.
  
    
  
    
🌱 A new release!
6.6.0 (2024-05-02)
The MongoDB Node.js team is pleased to announce version 6.6.0 of the
mongodbpackage!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
MongoMissingDependencyErrorsMongoMissingDependencyErrors now include acauseand adependencyNamefield, which can be used to programmatically determine which package is missing and why the driver failed to load it.For example:
ServerDescriptionRound Trip Time (RTT) measurement changes(1)
ServerDescription.roundTripTimeis now a moving averagePreviously,
ServerDescription.roundTripTimewas calculated as a weighted average of the most recently observed heartbeat duration and the previous duration. This update changes this behaviour to averageServerDescription.roundTripTimeover 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
minRoundTripTimetoServerDescriptionA new
minRoundTripTimeproperty is now available on theServerDescriptionclass 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.typesupported inSearchIndexDescriptionIt is now possible to specify the type of a search index when creating a search index:
Collection.findOneAndModify'sUpdateFilter.$currentDateno longer throws on collections with limited schemaExample:
TopologyDescriptionnow properly stringifies itself to JSONThe
TopologyDescriptionclass 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 usesMaps internally, which get serialized to{}when JSON stringified. We recommend using Node'sutil.inspect()helper to print topology descriptions becauseinspectproperly handles all JS types and all types we use in the driver. However, if JSON must be used, theTopologyDescriptionnow provides a customtoJSON()hook:Omit
readConcernandwriteConcerninCollection.listSearchIndexesoptions argumentImportant
readConcernandwriteConcernare no longer viable keys in the options argument passed intoCollection.listSearchIndexesThis type change is a correctness fix.
Collection.listSearchIndexesis an Atlas specific method, and Atlas' search indexes do not supportreadConcernandwriteConcernoptions. The types for this function now reflect this functionality.Don't throw error when non-read operation in a transaction has a
ReadPreferenceModeother than'primary'The following error will now only be thrown when a user provides a
ReadPreferenceModeother thanprimaryand 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
RunCommandOperationis treated as a read operation for this error.TopologyDescription.errortype isMongoErrorImportant
The
TopologyDescription.errorproperty type is nowMongoErrorrather thanMongoServerError.This type change is a correctness fix.
Before this change, the following errors that were not instances of
MongoServerErrorwere already passed intoTopologyDescription.errorat runtime:MongoNetworkError(excludingMongoNetworkRuntimeError)MongoErrorwith aMongoErrorLabel.HandshakeErrorlabelindexExists()no longer supports thefulloptionThe
Collection.indexExists()helper supported an option,full, that modified the internals of the method. Whenfullwas set totrue, the driver would always returnfalse, regardless of whether or not the index exists.The
fulloption 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.
ClusterTimeinterfacesignatureoptionalityThe
ClusterTimeinterface incorrectly reported thesignaturefield as required, the server may omit it, so the typescript has been updated to reflect reality.Summary
Features
timeoutMSanddefaultTimeoutMS(#4068) (ddd1e81)causeand package name for allMongoMissingDependencyErrors (#4067) (62ea94b)minRoundTripTimetoServerDescriptionand changeroundTripTimeto a moving average (#4059) (0e3d6ea)typeoption in create search index helpers (#4060) (3598c23)bsonto ^6.5.0 (#4035) (8ab2055)bsonto ^6.7.0 (#4099) (7f191cf)Bug Fixes
Collection.findOneAndModifyUpdateFilter.$currentDate(#4047) (a8670a7)ReadPreferenceModeother thanprimary(#4075) (39fc198)vtocreateIndexescommand whenversionis specified (#4043) (1879a04)TopologyDescription.errortype toMongoError(#4028) (30432e8)fullis set totrue(#4034) (0ebc1ac)libmongocryptafter fetching AWS KMS credentials (#4057) (c604e74)ClusterTime.signaturecan be undefined (#4069) (ce55ca9)Performance Improvements
setTimeoutcallback (#4094) (6abc074)Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.