Update mongodb 6.1.0 → 6.2.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ mongodb (6.1.0 → 6.2.0) · Repo · Changelog

Release Notes

6.2.0

6.2.0 (2023-10-19)

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

Release Notes

Updated to BSON 6.2.0

BSON now prints in full color! 🌈 🚀

See our release notes for BSON 6.2.0 here for more examples!

insertedIds in bulk write now contain only successful insertions

Prior to this fix, the bulk write error's result.insertedIds property contained the _id of each attempted insert in a bulk operation.

Now, when a bulkwrite() or an insertMany() operation rejects one or more inserts, throwing an error, the error's result.insertedIds property will only contain the _id fields of successfully inserted documents.

Fixed edge case leak in findOne()

When running a findOne against a time series collection, the driver left the implicit session for the cursor un-ended due to the way the server returns the resulting cursor information. Now the cursor will always be cleaned up regardless of the outcome of the find operation.

Removed client-side collection and database name validation

Database and collection name checking will now be in sync with the MongoDB server's naming restrictions. Specifically, users can now create collections that start or end with the '.' character.

Features

• NODE-5613: add awaited field to SDAM heartbeat events (#3895) (b50aadc)
• update bson to 6.2.0 (#3898) (32b7176)

Bug Fixes

• NODE-5496: remove client-side collection and database name check validation (#3873) (98550c6)
• NODE-5628: bulkWriteResult.insertedIds does not filter out _ids that are not actually inserted (#3867) (09f2a67)
• NODE-5706: make findOne() close implicit session to avoid memory leak (#3897) (995d138)

Documentation

• Reference
• API
• Changelog

We invite you to try the mongodb library immediately, and report any issues to the NODE project.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 14 commits:

• chore(main): release 6.2.0 [skip-ci] (#3876)
• test: remove mongosh integration tests (#3850)
• feat: update bson to 6.2.0 (#3898)
• fix(NODE-5706): make findOne() close implicit session to avoid memory leak (#3897)
• feat(NODE-5613): add `awaited` field to SDAM heartbeat events (#3895)
• refactor(NODE-5675): refactor server selection and connection checkout to use abort signals for timeout management (#3890)
• test(NODE-5704): fix explain tests (#3893)
• test(NODE-5694): update azure configuration (#3891)
• ci(NODE-5615): unit test on Node18 and Node20 (#3879)
• fix(NODE-5496): remove client-side collection and database name check validation (#3873)
• ci(NODE-5652): move vars to expansions (#3877)
• fix(NODE-5628): bulkWriteResult.insertedIds does not filter out _ids that are not actually inserted (#3867)
• test(NODE-4338): refactor auth prose tests (#3859)
• docs(no-story): add docs for 5.9 and 6.1 (#3869)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 32f2229

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR