[Snyk] Upgrade mongodb from 6.3.0 to 6.4.0 #10
Closed
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.3.0 to 6.4.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
6.4.0 (2024-02-29)
The MongoDB Node.js team is pleased to announce version 6.4.0 of the
mongodb
package!Release Notes
Server selection will use a different Mongos on retry
When retrying reads or writes on a sharded cluster, the driver will attempt to select a different mongos for the retry if multiple are present. This should heuristically avoid encountering the original error that caused the need to retry the operation.
Caching AWS credentials provider per client
Instead of creating a new AWS provider for each authentication, we cache the AWS credentials provider per client to prevent overwhelming the auth endpoint and ensure that cached credentials are not shared with other clients.
BSON upgraded to
^6.4.0
BSON has had a number of performance increases in the last two releases (6.3.0 and 6.4.0). Small basic latin (ASCII) only strings, small memory allocations (ObjectId and Decimal128) and numeric parsing operations (int32, doubles, and longs) have all had optimizations applied to them.
For details check out the release notes here: BSON 6.3.0 and BSON 6.4.0 🐎
ExceededTimeLimit was made a retryable reads error
Read operations will be retried after receiving an error with the
ExceededTimeLimit
label.Fixed unresolved request issue in KMS requester
Internal to the field-level encryption machinery is a helper that opens a TLS socket to the KMS provider endpoint and submits a KMS request. The code neglected to add a
'close'
event listener to the socket, which had the potential to improperly leave the promise pending indefinitely if no error was encountered.The base64 padding is now preserved in the saslContinue command
The authentication was rejected by the saslContinue command from mongosh due to missing "=" padding from the client. We fixed the way we parse payload to preserve trailing "="s.
countDocuments
now types the filter using the collection SchemaPreviously,
countDocuments
had a weakly typedDocument
type for the filter allowing any JS object as input. The filter is now typed asFilter<Schema>
to enable autocompletion, and, hopefully, catch minor bugs.Thank you to @ pashok88895 for contributing to this improvement.
The type error with
$addToSet
inbulkWrite
was fixedPreviously the following code sample would show a type error:
It happened because the driver's
Document
type falls back toany
, and internally we could not distinguish whether or not this assignment was intentional and should be allowed.After this change, users can extend their types from
Document
/any
, or use properties ofany
type and we skip the$addToSet
validation in those cases.Fixed heartbeat duration including socket creation
The ServerHeartbeatSucceeded and ServerHeartbeatFailed event have a duration property that represents the time it took to perform the
hello
handshake with MongoDB. The Monitor responsible for issuing heartbeats mistakenly included the time it took to create the socket in this field, which inflates the value with the time it takes to perform a DNS lookup, TCP, and TLS handshakes.Errors on cursor transform streams are now properly propagated.
These were previously swallowed and now will be emitted on the
error
event:The AWS token is now optional
Users may provide an
AWS_SESSION_TOKEN
as a client option or AWS configuration in addition to a username and password. But if the token is not provided, the driver won't throw an exception and let AWS SDK handle the request.Features
^6.4.0
(#4007) (90f2f70)^6.3.0
(#3983) (9401d09)Bug Fixes
Performance Improvements
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
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