Bump mongodb from 6.14.2 to 6.15.0

[dependabot]

Bumps mongodb from 6.14.2 to 6.15.0.

Release notes

Sourced from mongodb's releases.

v6.15.0

6.15.0 (2025-03-18)

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

Release Notes

Support for custom AWS credential providers

The driver now supports a user supplied custom AWS credentials provider for both authentication and for KMS requests when using client side encryption. The signature for the custom provider must be of () => Promise<AWSCredentials> which matches that of the official AWS SDK provider API. Provider chains from the actual AWS SDK can also be provided, allowing users to customize any of those options.

Example for authentication with a provider chain from the AWS SDK:

import { fromNodeProviderChain } from '@aws-sdk/credential-providers';
const client = new MongoClient(process.env.MONGODB_URI, {
authMechanismProperties: {
AWS_CREDENTIAL_PROVIDER: fromNodeProviderChain()
}
});

Example for using a custom provider for KMS requests only:

import { fromNodeProviderChain } from '@aws-sdk/credential-providers';
const client = new MongoClient(process.env.MONGODB_URI, {
autoEncryption: {
keyVaultNamespace: 'keyvault.datakeys',
kmsProviders: { aws: {} },
credentialProviders: {
aws: fromNodeProviderChain()
}
}
}

Custom providers do not need to come from the AWS SDK, they just need to be an async function that returns credentials:

const client = new MongoClient(process.env.MONGODB_URI, {
  authMechanismProperties: {
    AWS_CREDENTIAL_PROVIDER: async () => {
      return {
        accessKeyId: process.env.ACCESS_KEY_ID,
        secretAccessKey: process.env.SECRET_ACCESS_KEY
</tr></table> 

... (truncated)

Changelog

Sourced from mongodb's changelog.

6.15.0 (2025-03-18)

Features

• NODE-6141: allow custom aws sdk config (#4373) (3d047ed)

Bug Fixes

• NODE-6845: ensure internal rejections are handled (#4448) (06e941a)

Commits

• aa5a979 chore(main): release 6.15.0 [skip-ci] (#4463)
• 8a9f251 ci: skip flaky test in CSOT test suite (#4475)
• 78d951b docs: generate docs from latest main [skip-ci] (#4450)
• 2295824 ci: skip flaky test in abort signal test suite (#4470)
• e927f97 ci: skip flaky test in CSOT test suite (#4469)
• b36976e docs(NODE-6819): remove mention of yarn from readme and update server compa...
• d341a72 ci: skip flaky tests in FLE test suite (#4467)
• 0083b8e ci: skip flaky test in CSOT test suite (#4471)
• cd09d43 ci: skip flaky tests in retryable reads and sdam suites (#4466)
• 86d4ca1 ci(NODE-6519,NODE-6702): fix flaky listIndexes APM test and rtt calculation t...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)