[Snyk] Upgrade mongodb from 6.6.2 to 6.7.0

[afgallo]

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


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

• The recommended version was released on 21 days ago.

Release notes

Package name: mongodb

• 6.7.0 - 2024-05-29
  

  6.7.0 (2024-05-29)

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

  Release Notes

  Support for MONGODB-OIDC Authentication

  MONGODB-OIDC is now supported as an authentication mechanism for MongoDB server versions 7.0+. The currently supported facets to authenticate with are callback authentication, human interaction callback authentication, Azure machine authentication, and GCP machine authentication.

  Azure Machine Authentication

  The MongoClient must be instantiated with authMechanism=MONGODB-OIDC in the URI or in the client options. Additional required auth mechanism properties of TOKEN_RESOURCE and ENVIRONMENT are required and another optional username can be provided. Example:

  const client = new MongoClient('mongodb+srv://<username>@<host>:<port>/?authMechanism=MONGODB-OIDC&authMechanismProperties=TOKEN_RESOURCE:<azure_token>,ENVIRONMENT:azure');
  await client.connect();

  GCP Machine Authentication

  The MongoClient must be instantiated with authMechanism=MONGODB-OIDC in the URI or in the client options. Additional required auth mechanism properties of TOKEN_RESOURCE and ENVIRONMENT are required. Example:

  const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC&authMechanismProperties=TOKEN_RESOURCE:<gcp_token>,ENVIRONMENT:gcp');
  await client.connect();

  Callback Authentication

  The user can provide a custom callback to the MongoClient that returns a valid response with an access token. The callback is provided as an auth mechanism property an has the signature of:

  const oidcCallBack = (params: OIDCCallbackParams): Promise<OIDCResponse> => {
  // params.timeoutContext is an AbortSignal that will abort after 30 seconds for non-human and 5 minutes for human.
  // params.version is the current OIDC API version.
  // params.idpInfo is the IdP info returned from the server.
  // params.username is the optional username.

  // Make a call to get a token.
  const token = ...;
  return {
  accessToken: token,
  expiresInSeconds: 300,
  refreshToken: token
  };
  }

  const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC', {
  authMechanismProperties: {
  OIDC_CALLBACK: oidcCallback
  }
  });
  await client.connect();

  For callbacks that require human interaction, set the callback to the OIDC_HUMAN_CALLBACK property:

  const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC', {
    authMechanismProperties: {
      OIDC_HUMAN_CALLBACK: oidcCallback
    }
  });
  await client.connect();

  Fixed error when useBigInt64=true was set on Db or MongoClient

  Fixed an issue where when setting useBigInt64=true on MongoClients or Dbs an internal function compareTopologyVersion would throw an error when encountering a bigint value.

  Features

  • NODE-5464: OIDC machine and callback workflow (#3912) (2ba8434)

  Bug Fixes

  • NODE-6165: useBigInt64 causes compareTopologyVersion to throw (#4109) (21b729b)

  Documentation

  • Reference
  • API
  • Changelog

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

• 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

  • NODE-6171: RTT set to zero when serverMonitoringMode=stream (#4110) (7a7ec5b)

  Documentation

  • Reference
  • API
  • Changelog

  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.

---

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
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (8d122b0) to head (443f755).

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           87        87           
=========================================
  Hits            87        87           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.