[Snyk] Upgrade mongodb from 3.1.1 to 3.3.4 #14
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.
Snyk has created this PR to upgrade mongodb from 3.1.1 to 3.3.4.
ℹ️ 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.The recommended version fixes:
Release notes
The MongoDB Node.js team is pleased to announce version 3.3.4 of the driver
Release Highlights
This release primary consists of improvements to the "unified topology". In particular, a regression with interaction between the connection pool and topology could result in servers which "go away" (due to network error, for example) would not return, resulting in a
MongoTimeoutError
.Release Notes
Bug
Improvement
chore(release): 3.3.3
chore(release): 3.3.2
chore(release): 3.3.1
The MongoDB Node.js team is pleased to announce version 3.3.0 of the driver
Release Highlights
Server Version 4.2 feature support
This latest release brings support for features in the newly released MongoDB v4.2:
$merge
operatorSRV Polling for Sharded Clusters
The Driver has supported connecting to a cluster using an SRV record since version 3.0. Prior to now, we would only resolve the SRV record when initially connecting. This was fine for single replica sets, as the driver is able to discover new members added after initial connect from any member of a replica set. However, in a sharded deployment, individual mongos processes do not have an awareness of each other. This means that if the deployment changes in a shared cluster, the driver would have no way of knowing without disconnecting and connecting with a new client.
Starting in 3.3, if a driver connects to a sharded cluster with an SRV record, we will now periodically check that SRV record for any changes in the deployment, and update the client-side connections accordingly.
**NOTE: This feature is only available when starting a client with
{ useUnifiedTopology: true }
**Beta support for MongoDB Client-Side Encryption
The driver now has support for MongoDB Client-Side Encryption. This requires installing the
mongodb-client-encryption
npm package in your project.Merged
mongodb-core
intonode-mongodb-native
Up until this release, the
mongodb
driver has consisted of two components:mongodb-core
: The low-level engine of the driver.node-mongodb-native
: The API layer of the driver, published asmongodb
Over time, this separation has done more harm than good, and has led to increased development time for repairing bugs and implementing new features. Starting in the 3.3 release of
mongodb
, we have mergedmongodb-core
intonode-mongodb-native
, removing this barrier to development.Release Notes
Bug
Epic
New Feature
Task
Improvement
chore(release): 3.2.7
chore(release): 3.2.6
chore(release): 3.2.5
chore(release): 3.2.4
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