[Snyk] Upgrade mongodb from 4.3.1 to 4.5.0 #1
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade mongodb from 4.3.1 to 4.5.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: mongodb
The MongoDB Node.js team is pleased to announce version 4.5.0 of the mongodb package!
Release Highlights
This release includes a number of enhancements noted below.
comment
option supportThe
comment
option is now widely available: by setting acomment
on an operation you can trace its value in database logs for more insights.An example of a log line, trimmed for brevity. We can see the timestamp of the log and the time created on our client application differ.
Socket timeout fixes for FaaS environments
This release includes a fix for serverless environments where transient
serverHeartBeatFailure
events that could be corrected toserverHeartBeatSucceeded
events in the next tick of the event loop were nonetheless handled as an actual issue with the client's connection and caused unnecessary resource clean up routines.It turns out that since Node.js handles timeout events first in the event loop, socket timeouts expire while the FaaS environment is dormant and the timeout handler code is the first thing that runs upon function wake prior to checking for any data from the server. Delaying the timeout handling until after the data reading phase avoids the sleep-induced timeout error in the cases where the connection is still healthy.
TS fixes for 4.7
Typescript 4.7 may not be out yet but in preparation for its release we've fixed issues compiling against that version. The main new obstacle was defaulting generic arguments that require that the constraining condition enforce similarity with the defaulted type. You may notice that our change stream
watch<T extends Document = Document>()
methods now requires thatT
extends Document, a requirement that already had to be met by the underlyingChangeStreamDocument
type.Features
comment
field (#3167) (4e2f9bf)Bug Fixes
watch
type parameter to extendChangeStream
type parameter (#3183) (43ba9fc)Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
The MongoDB Node.js team is pleased to announce version 4.4.1 of the mongodb package!
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
The MongoDB Node.js team is pleased to announce version 4.4.0 of the mongodb package!
Release Highlights
This release includes a few new features described below.
KMIP
KMIP can now be configured as a KMS provider for CSFLE by providing the KMIP endpoint in the kmsProviders option.
Example:
CSFLE TLS
Custom TLS options can now be provided for connection to the KMS servers on a per KMS provider basis.
Example:
Valid options are
tlsCAFile
,tlsCertificateKeyFile
,tlsCertificateKeyFilePassword
and all accept strings as values: a string path to a certificate location on the file system or a string password.Kerberos
Hostname canonicalization when using GSSAPI authentication now accepts
'none'
,'forward'
, and'forwardAndReverse'
as auth mechanism properties.'none'
will perform no canonicalization (default),'forward'
will perform a forward cname lookup, and'forwardAndReverse'
will perform a forward lookup followed by a reverse PTR lookup on the IP address. Previous boolean values are still accepted and map tofalse -> 'none'
andtrue -> 'forwardAndReverse'
.Example:
For cases when the service host name differs from the connection’s host name (most likely when creating new users on localhost), a
SERVICE_HOST
auth mechanism property may now be provided.Example:
In the 4.0.0 release of the driver, the deprecated
collection.count()
method was inadvertently changed to behave likecollection.countDocuments()
. In this release, we have updated thecollection.count()
behavior to match the legacy behavior:collection.count
will behave the same ascollection.countDocuments
and perform a collection scan.collection.count
will behave the same ascollection.estimatedDocumentCount
and rely on collection metadata.We also deprecated the
cursor.count()
method and will remove it in the next major version along withcollection.count()
; please usecollection.estimatedDocumentCount()
orcollection.countDocuments()
instead.Features
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
Read more
Commit messages
Package name: mongodb
projection
to the query module Automattic/mongoose#3180)Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs