fix(deps): bump mongodb from 6.4.0 to 6.5.0
Bumps mongodb from 6.4.0 to 6.5.0.
Release notes
Sourced from mongodb's releases.
v6.5.0
6.5.0 (2024-03-11)
The MongoDB Node.js team is pleased to announce version 6.5.0 of the
mongodbpackage!Release Notes
Bulk Write Operations Generate Ids using
pkFactoryWhen performing inserts, the driver automatically generates
_ids for each document if there is no_idpresent. By default, the driver generatesObjectIds. An option,pkFactory, can be used to configure the driver to generate_ids that are not object ids.For a long time, only
Collection.insertandCollection.insertManyactually used thepkFactory, if configured. Notably,Collection.bulkWrite(),Collection.initializeOrderedBulkOp()andCollection.initializeOrderedBulkOp()always generatedObjectIds, regardless of what was configured on collection.The driver always generates
_ids for inserted documents using thepkFactory.[!CAUTION] If you are using a
pkFactoryand performing bulk writes, you may have inserted data into your database that does not have_ids generated by thepkFactory.Fixed applying read preference to commands depending on topology
When connecting to a secondary in a replica set with a direct connection, if a read operation is performed, the driver attaches a read preference of
primaryPreferredto the command.Fixed memory leak in Connection layer
The Connection class has recently been refactored to operate on our socket operations using promises. An oversight how we made async network operations interruptible made new promises for every operation. We've simplified the approach and corrected the leak.
Query SRV and TXT records in parallel
When connecting using a convenient SRV connection string (
mongodb+srv://) hostnames are obtained from an SRV dns lookup and some configuration options are obtained from a TXT dns query. Those DNS operations are now performed in parallel to reduce first-time connection latency.Container and Kubernetes Awareness
The Node.js driver now keeps track of container metadata in the
client.env.containerfield of the handshake document.If space allows, the following metadata will be included in
client.env.container:env?: { container?: { orchestrator?: 'kubernetes' // if process.env.KUBERNETES_SERVICE_HOST is set runtime?: 'docker' // if the '/.dockerenv' file exists } }Note: If neither Kubernetes nor Docker is present,
client.envwill not have thecontainerproperty.Add property
errorResponseto MongoServerErrorThe MongoServer error maps keys from the error document returned by the server on to itself. There are some use cases where the original error document is desirable to obtain in isolation. So now, the
mongoServerError.errorResponseproperty stores a reference to the error document returned by the server.
... (truncated)
Changelog
Sourced from mongodb's changelog.
6.5.0 (2024-03-11)
Features
- NODE-5968: container and Kubernetes awareness in client metadata (#4005) (28b7040)
- NODE-5988: Provide access to raw results doc on MongoServerError (#4016) (c023242)
- NODE-6008: deprecate CloseOptions interface (#4030) (f6cd8d9)
Bug Fixes
- NODE-5636: generate _ids using pkFactory in bulk write operations (#4025) (fbb5059)
- NODE-5981: read preference not applied to commands properly (#4010) (937c9c8)
- NODE-5985: throw Nodejs' certificate expired error when TLS fails to connect instead of
CERT_HAS_EXPIRED(#4014) (057c223)- NODE-5993: memory leak in the
Connectionclass (#4022) (69de253)Performance Improvements
Commits
c9e32adchore(main): release 6.5.0 [skip-ci] (#4013)f6cd8d9feat(NODE-6008): deprecate CloseOptions interface (#4030)36fa752refactor(NODE-5915): topology close logic to be synchronous (#4021)937c9c8fix(NODE-5981): read preference not applied to commands properly (#4010)31f1eedtest(NODE-5969): convert CSFLE corpus test #6 to TS, async/await and add writ...fbb5059fix(NODE-5636): generate _ids using pkFactory in bulk write operations (#4025)2348548test(DRIVERS-2812): sdam load balancer tests in serverless (#4026)c023242feat(NODE-5988): Provide access to raw results doc on MongoServerError (#4016)69de253fix(NODE-5993): memory leak in theConnectionclass (#4022)28b7040feat(NODE-5968): container and Kubernetes awareness in client metadata (#4005)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| fullstack-next | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 1, 2024 0:15am |
Superseded by #327.