# MongoDB Node.js Driver v7.0.0 - Product: MongoDB Node.js Driver (https://whatsnew.fyi/product/mongodb-node-driver) - Vendor: MongoDB - Date: 2025-11-06 - Version: v7.0.0 - Original notes: https://github.com/mongodb/node-mongodb-native/releases/tag/v7.0.0 - Permalink: https://whatsnew.fyi/product/mongodb-node-driver/releases/v7.0.0 What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'. --- - **changed** — Minimum supported Node.js version is now v20.19.0 - **changed** — TypeScript target has been updated to ES2023 - **added** — Native support for explicit resource management with Symbol.asyncDispose implementations on MongoClient, ClientSession, ChangeStream and cursors - **changed** — Driver updated to use bson@7.0.0 and mongodb-connection-string-url@7.0.0 - **changed** — Minimum version for @mongodb-js/zstd optional peer dependency raised to 7.0.0, dropped support for 1.x and 2.x - **changed** — Minimum version for kerberos optional peer dependency raised to 7.0.0, dropped support for 2.x - **changed** — Minimum version for mongodb-client-encryption optional peer dependency raised to 7.0.0, dropped support for 6.x - **changed** — Updated compatibility for @aws-sdk/credential-providers to ^3.806.0, gcp-metadata to ^7.0.1, and socks to ^2.8.6 - **changed** — @aws-sdk/credential-providers is now required for MONGODB-AWS authentication - **changed** — Custom AWS credential provider via AWS_CREDENTIAL_PROVIDER takes highest precedence over other AWS auth methods - **removed** — Explicitly provided credentials no longer accepted with MONGODB-AWS authentication in connection strings - **changed** — Dropping a collection returns false instead of throwing when namespace not found - **changed** — Aggregate with write concern and explain now throws MongoServerError instead of client-side error - **fixed** — All encryption-related errors now subclass MongoError - **fixed** — Fixed typo in error label from PoolRequstedRetry to PoolRequestedRetry ##### [7.0.0](https://github.com/mongodb/node-mongodb-native/compare/v6.20.0...v7.0.0) (2025-11-06) The MongoDB Node.js team is pleased to announce version 7.0.0 of the `mongodb` package! ##### Release Notes The following is a detailed collection of the changes in the major v7 release of the `mongodb` package for Node.js. The main focus of this release was usability improvements and a streamlined API. Read on for details! > [!IMPORTANT] > This is a list of changes relative to v6.21.0 of the driver. ALL changes listed below are BREAKING unless indicated otherwise. > Users migrating from an older version of the driver are advised to upgrade to at least v6.21.0 before adopting v7. ##### 🛠️ Runtime and dependency updates ###### Minimum Node.js version is now v20.19.0 The minimum supported Node.js version is now [v20.19.0](https://nodejs.org/en/blog/release/v20.19.0) and our TypeScript target has been updated to ES2023. We strive to keep our minimum supported Node.js version in sync with the runtime's [release cadence](https://nodejs.dev/en/about/releases/) to keep up with the latest security updates and modern language features. Notably, the driver now offers native support for explicit resource management. `Symbol.asyncDispose` implementations are available on the `MongoClient`, `ClientSession`, `ChangeStream` and on cursors. > [!Note] > Explicit resource management is considered experimental in the driver and will be until the [TC39 explicit resource management proposal](https://github.com/tc39/proposal-explicit-resource-management) is completed. ###### `bson` and `mongodb-connection-string-url` versions 7.0.0 This driver version has been updated to use `bson@7.0.0` and `mongodb-connection-string-url@7.0.0`, which match the driver's Node.js runtime version support. BSON functionality re-exported from the driver is furthermore subject to the changes outlined in the [BSON V7 release notes](https://github.com/mongodb/js-bson/releases/tag/v7.0.0). ###### Optional peer dependency releases and version bumps - `@mongodb-js/zstd` optional peer dependency minimum version raised to `7.0.0`, dropped support for `1.x` and `2.x` (note that `@mongodb-js/zstd` does not have `3.x-6.x` version releases) - `kerberos` optional peer dependency minimum version raised to `7.0.0`, dropped support for `2.x` (note that `kerberos` does not have `3.x-6.x` version releases) - `mongodb-client-encryption` optional peer dependency minimum version raised to `7.0.0`, dropped support for `6.x` Additionally, the driver is now compatible with the following packages: | Dependency | Previous Range | New Allowed Range | | ----------------------------- | -------------- | ----------------- | | @aws-sdk/credential-providers | ^3.188.0 | ^3.806.0 | | gcp-metadata | ^5.2.0 | ^7.0.1 | | socks | ^2.7.1 | ^2.8.6 | ##### 🔐 AWS authentication To improve long-term maintainability and ensure compatibility with AWS updates, we’ve standardized AWS auth to use the official SDK in all cases and made a number of supporting changes outlined below. ###### `@aws-sdk/credential-providers` is now required for MONGODB-AWS authentication Previous versions of the driver contained two implementations for AWS authentication and could run the risk of the custom driver implementation not supporting all AWS authentication features as well as not being correct when AWS makes changes. Using the official AWS SDK in all cases alleviates these issues. ```bash npm install @aws-sdk/credential-providers ``` ###### Custom AWS credential provider takes highest precedence When providing a custom AWS credential provider via the auth mechanism property `AWS_CREDENTIAL_PROVIDER`, it will now take the highest precedence over any other AWS auth method. ###### Explicitly provided credentials no longer accepted with MONGODB-AWS authentication AWS environments (such as AWS Lambd _[Truncated at 4000 characters — full notes: https://github.com/mongodb/node-mongodb-native/releases/tag/v7.0.0]_