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.

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

chore(deps): bump the driver group with 2 updates #754

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 3, 2024

Bumps the driver group with 2 updates: bson and mongodb.

Updates bson from 6.7.0 to 6.8.0

Release notes

Sourced from bson's releases.

v6.8.0

6.8.0 (2024-06-27)

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

Release Notes

Add Signature to Github Releases

The Github release for js-bson now contains a detached signature file for the NPM package (named bson-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.

Optimize performance of Long.fromBigInt

Internally fromBigInt was originally implemented using toString of the bigint value. Now, Long.fromBigInt has been refactored to use bitwise operations greatly improving performance.

Features

  • NODE-6156: add signature to github releases (#692) (f0fbe91)

Performance Improvements

  • NODE-6126: improve Long.fromBigInt performance (#681) (63eafcb)

Documentation

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

Changelog

Sourced from bson's changelog.

6.8.0 (2024-06-27)

Features

  • NODE-6156: add signature to github releases (#692) (f0fbe91)

Performance Improvements

  • NODE-6126: improve Long.fromBigInt performance (#681) (63eafcb)
Commits
  • ede8357 chore(main): release 6.8.0 [skip-ci] (#689)
  • de780bc docs(NODE-6235): update release integrity section (#702)
  • 676b797 chore: full ssdlc report (#701)
  • 36c8134 chore(NODE-6212): upload sbom to s3 during releases and use actions v2 (#700)
  • 8cf9323 chore: upgrade release signing to drivers-github-tools v2 (#696)
  • 9e7b76a chore(NODE-6170): update release please owner (#690)
  • b0f9264 chore: use sarif report action from main (#699)
  • cc2871e chore(NODE-6195): generate sarif reports during releases (#695)
  • 8c760d1 chore: incorrectly attempting access to sign release artifacts variables (#694)
  • f0fbe91 feat(NODE-6156): add signature to github releases (#692)
  • Additional commits viewable in compare view

Updates mongodb from 6.7.0 to 6.8.0

Release notes

Sourced from mongodb's releases.

v6.8.0

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.

... (truncated)

Changelog

Sourced from mongodb's changelog.

6.8.0 (2024-06-27)

Features

  • NODE-5718: add ReadConcernMajorityNotAvailableYet to retryable errors (#4154) (4f32dec)
  • NODE-5801: allow multiple providers providers per type (#4137) (4d209ce)
  • NODE-5853: support delegated KMIP data key option (#4129) (aa429f8)
  • NODE-6136: parse cursor responses on demand (#4112) (3ed6a2a)
  • NODE-6157: add signature to github releases (#4119) (f38c5fe)

Bug Fixes

  • NODE-5801: use more specific key typing for multiple KMS provider support (#4146) (465ffd9)
  • NODE-6085: add TS support for KMIP data key options (#4128) (f790cc1)
  • NODE-6241: allow Binary as local KMS provider key (#4160) (fb724eb)
  • NODE-6242: close becomes true after calling close when documents still remain (#4161) (e3d70c3)
Commits
  • 25c84a4 chore(main): release 6.8.0 [skip-ci] (#4125)
  • 9f447e9 chore(NODE-6243): move Node release tooling to drivers-github-tools (#4159)
  • e3d70c3 fix(NODE-6242): close becomes true after calling close when documents still r...
  • fb724eb fix(NODE-6241): allow Binary as local KMS provider key (#4160)
  • 4f32dec feat(NODE-5718): add ReadConcernMajorityNotAvailableYet to retryable errors (...
  • 27cb35b chore(NODE-6118): generate authorized publisher report and compliance report ...
  • 8fb43f8 chore(NODE-5974): sync CSOT tests (#4153)
  • 8d5d984 chore(NODE-6199): Update test/lambda/mongodb dependencies (#4145)
  • ec3caba test(NODE-6202): use single mongos in unacknowledged write tests (#4149)
  • c948d9c refactor: move CountDocument logic into collection API (#4148)
  • 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the driver group with 2 updates: [bson](https://github.com/mongodb/js-bson) and [mongodb](https://github.com/mongodb/node-mongodb-native).


Updates `bson` from 6.7.0 to 6.8.0
- [Release notes](https://github.com/mongodb/js-bson/releases)
- [Changelog](https://github.com/mongodb/js-bson/blob/main/HISTORY.md)
- [Commits](mongodb/js-bson@v6.7.0...v6.8.0)

Updates `mongodb` from 6.7.0 to 6.8.0
- [Release notes](https://github.com/mongodb/node-mongodb-native/releases)
- [Changelog](https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md)
- [Commits](mongodb/node-mongodb-native@v6.7.0...v6.8.0)

---
updated-dependencies:
- dependency-name: bson
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: driver
- dependency-name: mongodb
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: driver
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 3, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 21, 2024

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot bot closed this Nov 21, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/driver-c84d1dc9c6 branch November 21, 2024 09:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants