Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Upgrade mongodb from 6.5.0 to 6.9.0 #4224

Closed
wants to merge 1 commit into from
Closed

[Snyk] Upgrade mongodb from 6.5.0 to 6.9.0 #4224

wants to merge 1 commit into from

Conversation

prernaadev01
Copy link
Collaborator

Snyk has created this PR to upgrade mongodb from 6.5.0 to 6.9.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 64 versions ahead of your current version.
  • The recommended version was released a month ago, on 2024-09-12.
Release notes
Package name: mongodb
  • 6.9.0 - 2024-09-12
    Read more
  • 6.9.0-dev.20241003.sha.91f30357 - 2024-10-03
  • 6.9.0-dev.20241002.sha.d56e235c - 2024-10-02
  • 6.9.0-dev.20241001.sha.85f7dcf9 - 2024-10-01
  • 6.9.0-dev.20240928.sha.3f9d2437 - 2024-09-28
  • 6.9.0-dev.20240927.sha.681ddd8d - 2024-09-27
  • 6.9.0-dev.20240926.sha.3d3da407 - 2024-09-26
  • 6.9.0-dev.20240918.sha.643a8755 - 2024-09-18
  • 6.9.0-dev.20240917.sha.20396e1b - 2024-09-17
  • 6.9.0-dev.20240913.sha.8b0f3541 - 2024-09-13
  • 6.8.2 - 2024-09-12

    6.8.2 (2024-09-12)

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

    Release Notes

    Fixed mixed use of cursor.next() and cursor[Symbol.asyncIterator]

    In 6.8.0, we inadvertently prevented the use of cursor.next() along with using for await syntax to iterate cursors. If your code made use of the following pattern and the call to cursor.next retrieved all your documents in the first batch, then the for-await loop would never be entered. This issue is now fixed.

    const firstDoc = await cursor.next();

    for await (const doc of cursor) {
    // process doc
    // ...
    }

    Bug Fixes

    Documentation

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

  • 6.8.1 - 2024-09-06

    6.8.1 (2024-09-06)

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

    Release Notes

    Fixed enableUtf8Validation option

    Starting in v6.8.0 we inadvertently removed the ability to disable UTF-8 validation when deserializing BSON. Validation is normally a good thing, but it was always meant to be configurable and the recent Node.js runtime issues (v22.7.0) make this option indispensable for avoiding errors from mistakenly generated invalid UTF-8 bytes.

    Bug Fixes

    Documentation

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

  • 6.8.0 - 2024-06-27

    6.8.0 (2024-06-27)

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

    Release Notes

    Add ReadConcernMajorityNotAvailableYet to retryable errors

    ReadConcernMajorityNotAvailableYet (error code 134) is now a retryable read error.

    ClientEncryption.createDataKey() and other helpers now support named KMS providers

    KMS providers can now be associated with a name and multiple keys can be provided per-KMS provider. The following example configures a ClientEncryption object with multiple AWS keys:

    const clientEncryption = new ClientEncryption(keyVaultClient, {
    'aws:key1': {
    accessKeyId: ...,
    secretAccessKey: ...
    },
    'aws:key2': {
    accessKeyId: ...,
    secretAccessKey: ...
    },

    clientEncryption.createDataKey('aws:key-1', { ... });

    Named KMS providers are supported for azure, AWS, KMIP, local and gcp KMS providers. Named KMS providers cannot be used if the application is using the automatic KMS provider refresh capability.

    This feature requires mongodb-client-encryption>=6.0.1.

    KMIP data keys now support a delegated option

    When creating a KMIP data key, delegated can now be specified. If true, the KMIP provider will perform encryption / decryption of the data key locally, ensuring that the encryption key never leaves the KMIP server.

    clientEncryption.createDataKey('kmip', { masterKey: { delegated: true } } );

    This feature requires mongodb-client-encryption>=6.0.1.

    Cursor responses are now parsed lazily 🦥

    MongoDB cursors (find, aggregate, etc.) operate on batches of documents equal to batchSize. Each time the driver runs out of documents for the current batch it gets more (getMore) and returns each document one at a time through APIs like cursor.next() or for await (const doc of cursor).

    Prior to this change, the Node.js driver was designed in such a way that the entire BSON response was decoded after it was received. Parsing BSON, just like parsing JSON, is a synchronous blocking operation. This means that throughout a cursor's lifetime invocations of .next() that need to fetch a new batch hold up on parsing batchSize (default 1000) documents before returning to the user.

    In an effort to provide more responsiveness, the driver now decodes BSON "on demand". By operating on the layers of data returned by the server, the driver now receives a batch, and only obtains metadata like size, and if there are more documents to iterate after this batch. After that, each document is parsed out of the BSON as the cursor is iterated.

    A perfect example of where this comes in handy is our beloved mongosh! 💚

    test> db.test.find()
[
	{ _id: ObjectId('665f7fc5c9d5d52227434c65'), ... },
  ...
]
Type "it" for more

    That Type "it" for more message would now print after parsing only the documents displayed rather than after the entire batch is parsed.

    Add Signature to Github Releases

    The Github release for the mongodb package now contains a detached signature file for the NPM package (named
    mongodb-X.Y.Z.tgz.sig), on every major and patch release to 6.x and 5.x. To verify the signature, follow the instructions in the 'Release Integrity' section of the README.md file.

    The LocalKMSProviderConfiguration's key property accepts Binary

    A local KMS provider at runtime accepted a BSON Binary instance but the Typescript inaccurately only permitted Buffer and string.

    Clarified cursor state properties

    The cursor has a few properties that represent the current state from the perspective of the driver and server. This PR corrects an issue that never made it to a release but we would like to take the opportunity to re-highlight what each of these properties mean.

    • cursor.closed - cursor.close() has been called, and there are no more documents stored in the cursor.
    • cursor.killed - cursor.close() was called while the cursor still had a non-zero id, and the driver sent a killCursors command to free server-side resources
    • cursor.id == null - The cursor has yet to send it's first command (ex. find, aggregate)
    • cursor.id.isZero() - The server sent the driver a cursor id of 0 indicating a cursor no longer exists on the server side because all data has been returned to the driver.
    • cursor.bufferedCount() - The amount of documents stored locally in the cursor.

    Features

    Bug Fixes

    Documentation

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

  • 6.8.0-dev.20240912.sha.8347db9c - 2024-09-12
  • 6.8.0-dev.20240910.sha.833eaa41 - 2024-09-10
  • 6.8.0-dev.20240907.sha.91ceaf05 - 2024-09-07
  • 6.8.0-dev.20240905.sha.65e0e15c - 2024-09-05
  • 6.8.0-dev.20240904.sha.fb13ebfd - 2024-09-04
  • 6.8.0-dev.20240830.sha.1f10bdf8 - 2024-08-30
  • 6.8.0-dev.20240829.sha.6d65ae77 - 2024-08-29
  • 6.8.0-dev.20240824.sha.40ace73c - 2024-08-24
  • 6.8.0-dev.20240822.sha.f5254030 - 2024-08-22
  • 6.8.0-dev.20240821.sha.55bdeaa9 - 2024-08-21
  • 6.8.0-dev.20240813.sha.b70c8850 - 2024-08-13
  • 6.8.0-dev.20240808.sha.5565d500 - 2024-08-08
  • 6.8.0-dev.20240802.sha.54efb7d4 - 2024-08-02
  • 6.8.0-dev.20240731.sha.b26c3280 - 2024-07-31
  • 6.8.0-dev.20240727.sha.e9025843 - 2024-07-27
  • 6.8.0-dev.20240725.sha.74916f29 - 2024-07-25
  • 6.8.0-dev.20240720.sha.357ca086 - 2024-07-20
  • 6.8.0-dev.20240717.sha.35d88404 - 2024-07-17
  • 6.8.0-dev.20240716.sha.4b219d36 - 2024-07-16
  • 6.8.0-dev.20240712.sha.320dde04 - 2024-07-12
  • 6.8.0-dev.20240710.sha.fb442edc - 2024-07-10
  • 6.8.0-dev.20240709.sha.9a5e6110 - 2024-07-09
  • 6.8.0-dev.20240703.sha.5abf5fca - 2024-07-03
  • 6.8.0-dev.20240702.sha.f48f8d36 - 2024-07-02
  • 6.8.0-dev.20240629.sha.d85f827a - 2024-06-29
  • 6.8.0-dev.20240628.sha.45bc0982 - 2024-06-28
  • 6.7.0 - 2024-05-29
    Read more
  • 6.7.0-dev.20240627.sha.fb724eb6 - 2024-06-27
  • 6.7.0-dev.20240626.sha.4f32decc - 2024-06-26
  • 6.7.0-dev.20240625.sha.27cb35bb - 2024-06-25
  • 6.7.0-dev.20240621.sha.8fb43f86 - 2024-06-21
  • 6.7.0-dev.20240619.sha.8d5d9846 - 2024-06-19
  • 6.7.0-dev.20240618.sha.ec3cabaf - 2024-06-18
  • 6.7.0-dev.20240615.sha.465ffd97 - 2024-06-15
  • 6.7.0-dev.20240614.sha.3ed6a2ad - 2024-06-14
  • 6.7.0-dev.20240613.sha.c1af6adc - 2024-06-13
  • 6.7.0-dev.20240608.sha.0655c730 - 2024-06-08
  • 6.7.0-dev.20240607.sha.aa429f8c - 2024-06-07
  • 6.7.0-dev.20240530.sha.f56938f - 2024-05-30
  • 6.6.2 - 2024-05-15

    6.6.2 (2024-05-15)

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

    Release Notes

    Server Selection performance regression due to incorrect RTT measurement

    Starting in version 6.6.0, when using the stream server monitoring mode, heartbeats were incorrectly timed as having a duration of 0, leading to server selection viewing each server as equally desirable for selection.

    Bug Fixes

    Documentation

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

  • 6.6.2-dev.20240529.sha.d3031a5 - 2024-05-29
  • 6.6.2-dev.20240525.sha.d1695c4 - 2024-05-25
  • 6.6.2-dev.20240524.sha.652af8d - 2024-05-24
  • 6.6.2-dev.20240523.sha.21b729b - 2024-05-23
  • 6.6.2-dev.20240516.sha.6acb5e5 - 2024-05-16
  • 6.6.1 - 2024-05-06

    6.6.1 (2024-05-06)

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

    Release Notes

    ref()-ed timer keeps event loop running until client.connect() resolves

    When the MongoClient is first starting up (client.connect()) monitoring connections begin the process of discovering servers to make them selectable. The ref()-ed serverSelectionTimeoutMS timer keeps Node.js' event loop running as the monitoring connections are created. In the last release we inadvertently unref()-ed this initial timer which would allow Node.js to close before the monitors could create connections.

    Bug Fixes

    Documentation

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

  • 6.6.1-dev.20240511.sha.7c91272 - 2024-05-11
  • 6.6.1-dev.20240508.sha.f73362b - 2024-05-08
  • 6.6.1-dev.20240507.sha.706cc56 - 2024-05-07
  • 6.6.0 - 2024-05-03
    Read more
  • 6.6.0-dev.20240504.sha.2609953 - 2024-05-04
  • 6.5.0 - 2024-03-11
    Read more
from mongodb GitHub release notes
Commit messages
Package name: mongodb

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@prernaadev01 prernaadev01 requested review from a team as code owners October 8, 2024 19:25
@github-actions GitHub Actions
Copy link

github-actions bot commented Oct 8, 2024

Test Results

27 tests  ±0   27 ✅ ±0   0s ⏱️ ±0s
27 suites ±0    0 💤 ±0 
 3 files   ±0    0 ❌ ±0 

Results for commit b5a271e. ± Comparison against base commit 68bb322.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@andrewb1269hg andrewb1269hg Awaiting requested review from andrewb1269hg andrewb1269hg is a code owner automatically assigned from hashgraph/devops-ci

@mgarbs mgarbs Awaiting requested review from mgarbs mgarbs is a code owner automatically assigned from hashgraph/developer-advocates

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@prernaadev01 @snyk-bot