# MongoDB Node.js Driver v7.4.0

- Product: MongoDB Node.js Driver (https://whatsnew.fyi/product/mongodb-node-driver)
- Vendor: MongoDB
- Date: 2026-06-25
- Version: v7.4.0
- Original notes: https://github.com/mongodb/node-mongodb-native/releases/tag/v7.4.0
- Permalink: https://whatsnew.fyi/product/mongodb-node-driver/releases/v7.4.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** — Remove experimental tag from Symbol.asyncDispose methods on MongoClient, ClientSession, ChangeStream, and cursors to mark explicit resource management as stable
- **changed** — Send afterClusterTime on writes in causally-consistent sessions to maintain read your own writes guarantee across primary failovers in sharded clusters

##### [7.4.0](https://github.com/mongodb/node-mongodb-native/compare/v7.3.0...v7.4.0) (2026-06-25)

The MongoDB Node.js team is pleased to announce version 7.4.0 of the `mongodb` package!

##### Release Notes



###### Explicit resource management is now stable

The `Symbol.asyncDispose` methods on `MongoClient`, `ClientSession`, `ChangeStream`, and cursors enable `await using` for automatic cleanup. These methods were introduced as experimental in v6.9.0. Since then, TC39 Explicit Resource Management proposal reached Stage 4 in 2025, and Node.js enabled explicit resource management as a stable feature in Node.js 24, so the experimental flags have been removed from our APIs and the APIs are now officially supported.

###### afterClusterTime now sent on writes in causally-consistent sessions

When a session has causal consistency enabled, write operations now include `readConcern.afterClusterTime`, matching the existing read behavior. This maintains the "read your own writes" guarantee across primary failovers in shareded clusters. There are no API changes.
###### Features

* **NODE-7634:** remove experimental tag from async dispose methods ([#4976](https://github.com/mongodb/node-mongodb-native/issues/4976)) ([43ce3eb](https://github.com/mongodb/node-mongodb-native/commit/43ce3ebb701bf24af797d24e81788b576dccf1a9))
* **NODE-7549:** send afterClusterTime on writes in causally-consistent sessions ([#4963](https://github.com/mongodb/node-mongodb-native/issues/4963)) ([3abfd26](https://github.com/mongodb/node-mongodb-native/commit/3abfd263c5da2eaa5c223a0d5b9b440a1e1d4cf6))
##### Documentation



* [Reference](https://docs.mongodb.com/drivers/node/current/)
* [API](https://mongodb.github.io/node-mongodb-native/7.4/)
* [Changelog](https://github.com/mongodb/node-mongodb-native/blob/v7.4.0/HISTORY.md)

We invite you to try the `mongodb` library immediately, and report any issues to the [NODE project](https://jira.mongodb.org/projects/NODE).