[Snyk] Upgrade mongodb from 6.6.1 to 6.6.2 #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade mongodb from 6.6.1 to 6.6.2. See this package in npm: mongodb See this project in Snyk: https://app.snyk.io/org/axlecat284/project/469fb8d2-5612-454d-bdf4-ed4c2b67e214?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 6.6.1 to 6.6.2.
ℹ️ 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 is 6 versions ahead of your current version.
The recommended version was released on 22 days ago.
Release notes
Package name: mongodb
-
6.6.2 - 2024-05-15
- NODE-6171: RTT set to zero when serverMonitoringMode=stream (#4110) (7a7ec5b)
- Reference
- API
- Changelog
-
6.6.2-dev.20240529.sha.d3031a5 - 2024-05-29
-
6.6.2-dev.20240525.sha.d1695c4 - 2024-05-25
-
6.6.2-dev.20240524.sha.652af8d - 2024-05-24
-
6.6.2-dev.20240523.sha.21b729b - 2024-05-23
-
6.6.2-dev.20240516.sha.6acb5e5 - 2024-05-16
-
6.6.1 - 2024-05-06
- NODE-6151: MongoClient connect does not keep Node.js running (#4101) (7e0d9e6)
- Reference
- API
- Changelog
from mongodb GitHub release notes6.6.2 (2024-05-15)
The MongoDB Node.js team is pleased to announce version 6.6.2 of the
mongodbpackage!Release Notes
Server Selection performance regression due to incorrect RTT measurement
Starting in version 6.6.0, when using the
streamserver monitoring mode, heartbeats were incorrectly timed as having a duration of 0, leading to server selection viewing each server as equally desirable for selection.Bug Fixes
Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.6.6.1 (2024-05-06)
The MongoDB Node.js team is pleased to announce version 6.6.1 of the
mongodbpackage!Release Notes
ref()-ed timer keeps event loop running untilclient.connect()resolvesWhen the
MongoClientis first starting up (client.connect()) monitoring connections begin the process of discovering servers to make them selectable. Theref()-edserverSelectionTimeoutMStimer keeps Node.js' event loop running as the monitoring connections are created. In the last release we inadvertentlyunref()-ed this initial timer which would allow Node.js to close before the monitors could create connections.Bug Fixes
Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.Important
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: