Repository navigation
chore(main): release 7.8.0 - #5070
Merged
dariakp merged 1 commit intoOct 30, 2026
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main--components--mongodb
branch
2 times, most recently
from
October 7, 2026 21:11
b84e9c8 to
24f5768
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--mongodb
branch
4 times, most recently
from
October 9, 2026 10:09
800781f to
30303a3
Compare
Contributor
|
run release_notes |
github-actions
Bot
force-pushed
the
release-please--branches--main--components--mongodb
branch
from
October 15, 2026 09:25
30303a3 to
d51cd72
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--mongodb
branch
3 times, most recently
from
October 29, 2026 16:41
ef823a5 to
e293d02
Compare
Contributor
|
run release_notes |
github-actions
Bot
force-pushed
the
release-please--branches--main--components--mongodb
branch
from
October 29, 2026 22:29
e293d02 to
a5f31ed
Compare
Contributor
|
run release_notes |
github-actions
Bot
force-pushed
the
release-please--branches--main--components--mongodb
branch
from
October 30, 2026 01:30
a5f31ed to
041a18c
Compare
Member
|
run release_notes |
tadjik1
approved these changes
Oct 30, 2026
github-actions
Bot
force-pushed
the
release-please--branches--main--components--mongodb
branch
from
October 30, 2026 11:56
041a18c to
510042e
Compare
johnmtll
approved these changes
Oct 30, 2026
dariakp
deleted the
release-please--branches--main--components--mongodb
branch
October 30, 2026 16:23
Contributor
Author
|
🤖 Created releases: 🌻 |
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
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.
🌱 A new release!
7.8.0 (2026-10-30)
The MongoDB Node.js team is pleased to announce version 7.8.0 of the
mongodbpackage!Release Notes
timeoutMSis deprecated and now a no-opWarning
timeoutMSandtimeoutModeare deprecated and have no effect starting in this release. They are still accepted and will not throw, but operations will no longer time out because of them. They are slated for removal in a future release.Use the per-stage timeouts instead:
serverSelectionTimeoutMS,waitQueueTimeoutMS,socketTimeoutMS, andmaxTimeMSfor server-side execution.Configurable SRV host validation
This release adds two new methods of validating DNS:
srvAllowedHostsSuffix- A host name suffix that every host returned by the SRV lookup must end with. This option can be configured on the client or the connection string.srvHostValidator- A synchronous function that decides whether a host returned by the SRV lookup may be used. This option can only be configured on the client. This function must accept a string and has to return a boolean; returning anything else, including the Promise returned by anasyncfunction, will result in an error.Warning
Modifying the default SRV domain name validation can create vulnerabilities.
SRV host names are now compared in a normalized form (case-insensitively, without a trailing dot, and with internationalized names in
xn--form). Connection strings whose SRV host name differs in case from the host names returned by DNS, such asmongodb+srv://TEST1.TEST.BUILD.10GEN.CC, previously failed SRV verification and now connect.zstd compression no longer requires
@mongodb-js/zstdon Node.js 22.15.0+The driver now uses Node.js' built-in zstd implementation when it is available. On older Node.js versions it continues to use
@mongodb-js/zstd, so no changes are needed for existing setups.Thanks to @axelonet for the original contribution!
Distinguish between command-level options and index-level options when creating indexes
Before:
After:
Both overloads will be supported for now. In a future major release, the two parameter overload will be removed.
Enjoy faster adoption of new index options
Before:
After:
The two-parameter overload will continue to filter for valid index options. In a future major release, the two parameter overload will be removed.
Removed
@experimentaltags from features which are no-longer experimentalNo-longer experimental entities:
DropCollectionOptions.encryptedFieldsCreateCollectionOptions.encryptedFieldsClientEncryptionCreateDataKeyProviderOptions.keyMaterialClientEncryptionRewrapManyDataKeyProviderOptionsClientEncryptionRewrapManyDataKeyResultAlongside these changes is also a change to the return type of
rewrapManyDataKeytoClientEncryptionRewrapManyDataKeyResultfrom an anonymous type. This improves internal type consistency and public api clarity without changing runtime behavior.Sorting by
$metawith a[field, direction]pair now worksPreviously, passing a
$metasort direction in the[field, direction]form, for examplecursor.sort(['score', { $meta: 'textScore' }]), threwMongoInvalidArgumentError: Invalid sort direction. The object form ({ score: { $meta: 'textScore' } }) and the nested array form ([['score', { $meta: 'textScore' }]]) already worked, so the same sort was accepted or rejected depending on how it was written. All three forms now behave the same.Thanks to @spokodev for the fix!
Fix bulk write result
insertedIdsmismatches on bulkwrites with mixed op typesFor unordered bulk writes that mixed inserts with updates or deletes, BulkWriteResult.insertedIds was keyed by a running count of inserts, not by each insert's index in the operations list. It's now keyed by the operation index, which matches ordered bulk writes and the documentation.
Thanks to @spokodev for this fix!
GridFS queries match file IDs exactly
GridFS download, delete, rename and upload abort now query by file ID with
$eq. Nothing changes for normal IDs, but you'll see{ _id: { $eq: <id> } }in command monitoring and logs.hellocommands are no longer compressedWhen
compressorswas configured, the driver could sendhelloandisMasteron monitoring connections as compressed messages, which the compression specification forbids. These commands are now never compressed.Features
Bug Fixes
Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.