[Snyk] Upgrade mongodb from 6.14.0 to 6.14.2 #671
Conversation
This file contains hidden or 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.14.0 to 6.14.2. See this package in npm: mongodb See this project in Snyk: https://app.snyk.io/org/bryopsida/project/0a41dac2-c12e-420a-b72d-14f26e7a47de?utm_source=github&utm_medium=referral&page=upgrade-pr
|
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
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.
Snyk has created this PR to upgrade mongodb from 6.14.0 to 6.14.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 11 versions ahead of your current version.
The recommended version was released 22 days ago.
Release notes
Package name: mongodb
-
6.14.2 - 2025-03-04
- NODE-6803: kms proxy socket creates unhandled rejection (#4444) (ed69cf9)
- Reference
- API
- Changelog
-
6.14.2-dev.20250318.sha.78d951b9 - 2025-03-18
-
6.14.2-dev.20250315.sha.cd09d435 - 2025-03-15
-
6.14.2-dev.20250314.sha.6895b258 - 2025-03-14
-
6.14.2-dev.20250313.sha.54d29e56 - 2025-03-13
-
6.14.2-dev.20250312.sha.5783db21 - 2025-03-12
-
6.14.2-dev.20250310.sha.39c76999 - 2025-03-10
-
6.14.2-dev.20250306.sha.21072009 - 2025-03-06
-
6.14.2-dev.20250305.sha.398e361f - 2025-03-05
-
6.14.1 - 2025-03-03
- NODE-6801: set token on connection from cache (#4438) (cb13746)
- Reference
- API
- Changelog
-
6.14.1-dev.20250304.sha.3cc3a6b2 - 2025-03-04
-
6.14.0 - 2025-02-28
- NODE-6676: add support for
- NODE-6773: add support for $lookup with automatic encryption (#4427) (965b21a)
- NODE-6765: FindOneAndUpdateOptions supports aggregation expressions (#4423) (421ddeb)
- NODE-6792: use isUint8Array from driver's utils instead of util/types (#4436) (dfe1fba)
- NODE-6794: revert
- Reference
- API
- Changelog
from mongodb GitHub release notes6.14.2 (2025-03-04)
The MongoDB Node.js team is pleased to announce version 6.14.2 of the
mongodbpackage!Release Notes
KMS Requests can cause unhandled rejection
When using explicit encryption or automatic encryption, the driver makes requests to a Key Management System when to fetch key encryption keys. The driver supports connecting to a KMS provider through a Socks5 proxy. However, the socket used for the socks5 proxy was created in all circumstances, regardless of proxy configuration. This leads to unhandled rejection errors when closing the socket the driver attempts to clean up the unused socket.
With the changes in this release, the socket is only created if a proxy is configured and the any promises created for the proxy are properly handled.
Bug Fixes
Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.6.14.1 (2025-03-03)
The MongoDB Node.js team is pleased to announce version 6.14.1 of the
mongodbpackage!Release Notes
Fixed occasional OIDC reauthentication failure
Error code 391 is intended to make the driver internally reauthenticate the connection to the server, however, occasionally this was being raised to the user. This was due to a bug in setting the cached access token on newly created connections.
Bug Fixes
Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.6.14.0 (2025-02-28)
The MongoDB Node.js team is pleased to announce version 6.14.0 of the
mongodbpackage!Release Notes
Add support for $lookup on encrypted collections
Starting in the upcoming MongoDB server 8.1, the aggregation stage
$lookupcan now be used with clients configured for automatic encryption after upgrading tomongodb-client-encryption@>=6.3.0! 🔒 🎉Use
isUint8Arraydefined in the driver rather thanutil/typesSome users of bundlers for next.js and our very own mongosh noticed a new import from "util/types" that would need to be supported in environments that don't have that module. We already have an internal implementation of
isUint8Arrayso we do not need to add an import for "util/types".Revert
@ aws-sdk/credential-providerscompatiblity changeIn v6.13.1 we inadvertantly raised the version compatibility of
@ aws-sdk/credential-providers, that change has been reverted.Features
nsTypein change stream create events (#4431) (7800067)Bug Fixes
@ aws-sdk/credential-providerspeer compatibility change (#4437) (488c407)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: