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.6.0 #10

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade mongodb from 6.5.0 to 6.6.0 #10

wants to merge 1 commit into from

Conversation

tdbaine
Copy link
Collaborator

@tdbaine tdbaine commented May 24, 2024

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade mongodb from 6.5.0 to 6.6.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 2 versions ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: mongodb
  • 6.6.0 - 2024-05-03

    6.6.0 (2024-05-02)

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

    Release Notes

    Aggregation pipelines can now add stages manually

    When creating an aggregation pipeline cursor, a new generic method addStage() has been added in the fluid API for users to add aggregation pipeline stages in a general manner.

    const documents = await users.aggregate().addStage({ $project: { name: true } }).toArray();

    Thank you @ prenaissance for contributing this feature!

    cause and package name included for MongoMissingDependencyErrors

    MongoMissingDependencyErrors now include a cause and a dependencyName field, which can be used to programmatically determine which package is missing and why the driver failed to load it.

    For example:

    MongoMissingDependencyError: The iHateJavascript module does not exist
    at findOne (mongodb/main.js:7:11)
    at Object.<anonymous> (mongodb/main.js:14:1)
    ... 3 lines matching cause stack trace ...
    at Module._load (node:internal/modules/cjs/loader:1021:12) {
  dependencyName: 'iHateJavascript',
  [Symbol(errorLabels)]: Set(0) {},
  [cause]: Error: Cannot find module 'iHateJavascript'
  Require stack:
  - mongodb/main.js
      at require (node:internal/modules/helpers:179:18)
      at findOne (mongodb/main.js:5:5)
      at Object.<anonymous> (mongodb/main.js:14:1) {
    code: 'MODULE_NOT_FOUND',
    requireStack: [ 'mongodb/main.js' ]
  }
}

    ServerDescription Round Trip Time (RTT) measurement changes

    (1) ServerDescription.roundTripTime is now a moving average

    Previously, ServerDescription.roundTripTime was calculated as a weighted average of the most recently observed heartbeat duration and the previous duration. This update changes this behaviour to average ServerDescription.roundTripTime over the last 10 observed heartbeats. This should reduce the likelihood that the selected server changes as a result of momentary spikes in server latency.

    (2) Added minRoundTripTime to ServerDescription

    A new minRoundTripTime property is now available on the ServerDescription class which gives the minimum RTT over the last 10 heartbeats. Note that this value will be reported as 0 when fewer than 2 samples have been observed.

    type supported in SearchIndexDescription

    It is now possible to specify the type of a search index when creating a search index:

    const indexName = await collection.createSearchIndex({
  name: 'my-vector-search-index',
  // new! specifies that a `vectorSearch` index is created
  type: 'vectorSearch',
  definition: {
    mappings: { dynamic: false }
  }
});

    Collection.findOneAndModify's UpdateFilter.$currentDate no longer throws on collections with limited schema

    Example:

    // collection has no schema
collection.update(
    $currentData: {
       lastModified: true
    } // no longer throws a TS error
);

    TopologyDescription now properly stringifies itself to JSON

    The TopologyDescription class is exposed by the driver in server selection errors and topology monitoring events to provide insight into the driver's current representation of the server's topology and to aid in debugging. However, the TopologyDescription uses Maps internally, which get serialized to {} when JSON stringified. We recommend using Node's util.inspect() helper to print topology descriptions because inspect properly handles all JS types and all types we use in the driver. However, if JSON must be used, the TopologyDescription now provides a custom toJSON() hook:

    client.on('topologyDescriptionChanged', ({ newDescription }) => {
    // recommended!
    console.log('topology description changed', inspect(newDescription, { depth: Infinity, colors: true }))

    <span class="pl-c">// now properly prints the entire topology description</span>
<span class="pl-smi">console</span><span class="pl-kos">.</span><span class="pl-en">log</span><span class="pl-kos">(</span><span class="pl-s">'topology description changed'</span><span class="pl-kos">,</span> <span class="pl-smi">JSON</span><span class="pl-kos">.</span><span class="pl-en">stringify</span><span class="pl-kos">(</span><span class="pl-s1">newDescription</span><span class="pl-kos">)</span><span class="pl-kos">)</span>

    });

    Omit readConcern and writeConcern in Collection.listSearchIndexes options argument

    Important

    readConcern and writeConcern are no longer viable keys in the options argument passed into Collection.listSearchIndexes

    This type change is a correctness fix.

    Collection.listSearchIndexes is an Atlas specific method, and Atlas' search indexes do not support readConcern and writeConcern options. The types for this function now reflect this functionality.

    Don't throw error when non-read operation in a transaction has a ReadPreferenceMode other than 'primary'

    The following error will now only be thrown when a user provides a ReadPreferenceMode other than primary and then tries to perform a command that involves a read:

    new MongoTransactionError('Read preference in a transaction must be primary');

    Prior to this change, the Node Driver would incorrectly throw this error even when the operation does not perform a read.
    Note: a RunCommandOperation is treated as a read operation for this error.

    TopologyDescription.error type is MongoError

    Important

    The TopologyDescription.error property type is now MongoError rather than MongoServerError.

    This type change is a correctness fix.

    Before this change, the following errors that were not instances of MongoServerError were already passed into TopologyDescription.error at runtime:

    • MongoNetworkError (excluding MongoNetworkRuntimeError)
    • MongoError with a MongoErrorLabel.HandshakeError label

    indexExists() no longer supports the full option

    The Collection.indexExists() helper supported an option, full, that modified the internals of the method. When full was set to true, the driver would always return false, regardless of whether or not the index exists.

    The full option is intended to modify the return type of index enumeration APIs (Collection.indexes() and Collection.indexInformation(), but since the return type of Collection.indexExists() this option does not make sense for the Collection.indexExists() helper.

    We have removed support for this option.

    indexExists(), indexes() and indexInformation() support cursor options in Typescript

    These APIs have supported cursor options at runtime since the 4.x version of the driver, but our Typescript has incorrectly omitted cursor options from these APIs.

    Index information helpers have accurate Typescript return types

    Collection.indexInformation(), Collection.indexes() and Db.indexInformation() are helpers that return index information for a given collection or database. These helpers take an option, full, that configures whether the return value contains full index descriptions or a compact summary:

    collection.indexes({ full: true });   // returns an array of index descriptions
collection.indexes({ full: false });  // returns an object, mapping index names to index keys

    However, the Typescript return type of these helpers was always Document. Thanks to @ prenaissance, these helpers now have accurate type information! The helpers return a new type, IndexDescriptionCompact | IndexDescriptionInfo[], which accurately reflects the return type of these helpers. The helpers also support type narrowing by providing a boolean literal as an option to the API:

    collection.indexes(); // returns IndexDescriptionCompact | IndexDescriptionInfo[]
    collection.indexes({ full: false }); // returns an IndexDescriptionCompact
    collection.indexes({ full: true }); // returns an IndexDescriptionInfo[]

    collection.indexInfo(); // returns IndexDescriptionCompact | IndexDescriptionInfo[]
    collection.indexInfo({ full: false }); // returns an IndexDescriptionCompact
    collection.indexInfo({ full: true }); // returns an IndexDescriptionInfo[]

    db.indexInfo(); // returns IndexDescriptionCompact | IndexDescriptionInfo[]
    db.indexInfo({ full: false }); // returns an IndexDescriptionCompact
    db.indexInfo({ full: true }); // returns an IndexDescriptionInfo[]

    AWS credentials with expirations no longer throw when using on-demand AWS KMS credentials

    In addition to letting users provide KMS credentials manually, client-side encryption supports fetching AWS KMS credentials on-demand using the AWS SDK. However, AWS credential mechanisms that returned access keys with expiration timestamps caused the driver to throw an error.

    The driver will no longer throw an error when receiving an expiration token from the AWS SDK.

    ClusterTime interface signature optionality

    The ClusterTime interface incorrectly reported the signature field as required, the server may omit it, so the typescript has been updated to reflect reality.

    Summary

    Features

    Bug Fixes

    Performance Improvements

    Documentation

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

  • 6.6.0-dev.20240504.sha.2609953 - 2024-05-04
  • 6.5.0 - 2024-03-11

    6.5.0 (2024-03-11)

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

    Release Notes

    Bulk Write Operations Generate Ids using pkFactory

    When performing inserts, the driver automatically generates _ids for each document if there is no _id present. By default, the driver generates ObjectIds. An option, pkFactory, can be used to configure the driver to generate _ids that are not object ids.

    For a long time, only Collection.insert and Collection.insertMany actually used the pkFactory, if configured. Notably, Collection.bulkWrite(), Collection.initializeOrderedBulkOp() and Collection.initializeOrderedBulkOp() always generated ObjectIds, regardless of what was configured on collection.

    The driver always generates _ids for inserted documents using the pkFactory.

    Caution

    If you are using a pkFactory and performing bulk writes, you may have inserted data into your database that does not have _ids generated by the pkFactory.

    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 primaryPreferred to 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.container field 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.env will not have the container property.

    Add property errorResponse to MongoServerError

    The 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.errorResponse property stores a reference to the error document returned by the server.

    Deprecated unused CloseOptions interface

    The CloseOptions interface was unintentionally made public and was only intended for use in the driver's internals. Due to recent refactoring (NODE-5915), this interface is no longer used in the driver. Since it was marked public, out of an abundance of caution we will not be removing it outside of a major version, but we have deprecated it and will be removing it in the next major version.

    Features

    Bug Fixes

    Performance Improvements

    Documentation

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

from mongodb GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Snyk has automatically assigned this pull request, set who gets assigned.

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:

@snyk-bot
fix: upgrade mongodb from 6.5.0 to 6.6.0
cf80f8d 
Snyk has created this PR to upgrade mongodb from 6.5.0 to 6.6.0.

See this package in npm:
mongodb

See this project in Snyk:
https://app.snyk.io/org/tdbaine/project/a6bb9aff-5e66-4082-8f00-d0af520a23f0?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@odcampbell odcampbell

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@tdbaine @odcampbell @snyk-bot