keystonejs / keystone-5

https://v5.keystonejs.com
MIT License
64 stars 33 forks source link

Update dependency mongodb to ^3.7.0 #300

Closed renovate[bot] closed 3 years ago

renovate[bot] commented 3 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mongodb ^3.6.9 -> ^3.7.0 age adoption passing confidence

Release Notes

mongodb/node-mongodb-native ### [`v3.7.0`](https://togithub.com/mongodb/node-mongodb-native/releases/v3.7.0) [Compare Source](https://togithub.com/mongodb/node-mongodb-native/compare/v3.6.12...v3.7.0) The MongoDB Node.js team is pleased to announce version 3.7.0 of the mongodb package! ##### Release Highlights ##### Versioned API Versioned API is a new feature in MongoDB 5.0 that allows user-selectable API versions, subsets of MongoDB server semantics, to be declared on a client. During communication with a server, clients with a declared API version will force the server to behave in a manner compatible with the API version. Declaring an API version on a client can be used to ensure consistent responses from a server, providing long term API stability for an application. The declared API version is applied to all commands run through the client, including those sent through the generic RunCommand helper. Specifying versioned API options in the command document AND declaring an API version on the client is not supported and will lead to undefined behavior. ##### Declare an API version on a client ```javascript // Declare API version "1" for the client client = new MongoClient(uri, { serverApi: { version: '1' } }); cursor = client.db('database').collection('coll').find(...); ``` ##### Strict mode Declaring a `strict` API version will cause the MongoDB server to reject all commands that are not part of the declared API version. This includes command options and aggregation pipeline stages. For example, the following `find` call would fail because the `tailable` option is not part of version 1: ```javascript // Declare API version "1" for the client, with strict on client = new MongoClient(uri, { serverApi: { version: '1', strict: true } }); // Fails with an error cursor = client.db('database').collection('coll').find({ ... }, { tailable: true }); ``` ##### Deprecation Errors The `deprecationErrors` option can be used to enable command failures when using functionality that is deprecated from version 1. Note that at the time of this writing, no deprecations in version 1 exist. ```javascript // Declare API version "1" for the client, with deprecationErrors on client = new MongoClient(uri, { serverApi: { version: '1', deprecationErrors: true } }); // Note: since API version "1" is the initial version, there are no deprecated commands to provide as an example yet. ``` ##### Features - **NODE-3191:** backport versioned api ([#​2850](https://togithub.com/mongodb/node-mongodb-native/issues/2850)) ([93a47fd](https://togithub.com/mongodb/node-mongodb-native/commit/93a47fdbd92a27f0821cbcf59a951d581bfec9c0)) ##### Bug Fixes - **NODE-3377:** driver should allow arbitrary explain levels ([#​2961](https://togithub.com/mongodb/node-mongodb-native/issues/2961)) ([96c8ab4](https://togithub.com/mongodb/node-mongodb-native/commit/96c8ab41e38eb5a4c012b4cd5df3ab8c59a5d9fe)) - **NODE-3463:** pass explain error through to callback ([#​2949](https://togithub.com/mongodb/node-mongodb-native/issues/2949)) ([e5975af](https://togithub.com/mongodb/node-mongodb-native/commit/e5975af98615b2e0ef82b0031d4ec687d5a85109)) ##### Documentation - Reference: https://docs.mongodb.com/drivers/node/current/ - API: https://mongodb.github.io/node-mongodb-native/3.7/api/ - Changelog: https://github.com/mongodb/node-mongodb-native/blob/v3.7.0/HISTORY.md We invite you to try the mongodb library immediately, and report any issues to the [NODE project](https://jira.mongodb.org/projects/NODE). ### [`v3.6.12`](https://togithub.com/mongodb/node-mongodb-native/releases/v3.6.12) [Compare Source](https://togithub.com/mongodb/node-mongodb-native/compare/v3.6.11...v3.6.12) The MongoDB Node.js team is pleased to announce version 3.6.12 of the mongodb package! ##### Bug Fixes - **NODE-3487:** check for nullish aws mechanism property ([#​2957](https://togithub.com/mongodb/node-mongodb-native/issues/2957)) ([5902b4c](https://togithub.com/mongodb/node-mongodb-native/commit/5902b4c13a977c659af94b1fbcbcfbe5e7ca4db4)) - **NODE-3528:** add support for snappy v7 ([#​2947](https://togithub.com/mongodb/node-mongodb-native/issues/2947)) ([54f5c2d](https://togithub.com/mongodb/node-mongodb-native/commit/54f5c2d682828bc751242cf4e90ea73f0342c842)) ##### Documentation - Reference: https://docs.mongodb.com/drivers/node/current/ - API: https://mongodb.github.io/node-mongodb-native/3.6/api/ - Changelog: https://github.com/mongodb/node-mongodb-native/blob/v3.6.12/HISTORY.md We invite you to try the mongodb library immediately, and report any issues to the [NODE project](https://jira.mongodb.org/projects/NODE). ### [`v3.6.11`](https://togithub.com/mongodb/node-mongodb-native/releases/v3.6.11) [Compare Source](https://togithub.com/mongodb/node-mongodb-native/compare/v3.6.10...v3.6.11) The MongoDB Node.js team is pleased to announce version 3.6.11 of the mongodb package! #### Release Highlights This patch addresses a few bugs listed below. Notably, we fixed an issue with the way we imported one of our optional dependencies that blocked webpack bundling. If you are a webpack user you will still get warnings for our optional dependencies (if you don't use them). You can hush the warnings by adding [this option](https://webpack.js.org/configuration/externals/) to your webpack config: ```javascript { // ... externals: [ 'mongodb-client-encryption', 'aws4', 'saslprep', 'kerberos', 'snappy', 'bson-ext', ], // ... } ``` It is important to note that this will leave the imports in place and not pull in the code to your bundle. If you later do adopt using these dependencies you'll want to revert the relevant setting. ##### Bug Fixes - **NODE-1843:** bulk operations ignoring provided sessions ([#​2898](https://togithub.com/mongodb/node-mongodb-native/issues/2898)) ([9244b17](https://togithub.com/mongodb/node-mongodb-native/commit/9244b1771e538f7b685fd6d4aa83d9da84b20093)) - **NODE-3199:** unable to bundle driver due to uncaught require ([#​2903](https://togithub.com/mongodb/node-mongodb-native/issues/2903)) ([60efe9d](https://togithub.com/mongodb/node-mongodb-native/commit/60efe9d0030477da462d326c2e2ddc5fe6c0ffff)) #### Documentation - Reference: https://docs.mongodb.com/drivers/node/current/ - API: http://mongodb.github.io/node-mongodb-native/3.6/api - Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.6/HISTORY.md We invite you to try the mongodb package immediately, and report any issues to the [NODE project](https://jira.mongodb.org/projects/NODE). ### [`v3.6.10`](https://togithub.com/mongodb/node-mongodb-native/releases/v3.6.10) [Compare Source](https://togithub.com/mongodb/node-mongodb-native/compare/v3.6.9...v3.6.10) The MongoDB Node.js team is pleased to announce version 3.6.10 of the mongodb package! ##### Release Highlights This patch addresses a few bugs listed below. Notably the `bsonRegExp` option is now respected by the underlying BSON library, you can use this to decode regular expressions that contain syntax not permitted in native JS RegExp objects. Take a look at this example: ```javascript await collection.insertOne({ a: new BSONRegExp('(?-i)AA_') }) await collection.findOne({ a: new BSONRegExp('(?-i)AA_') }, { bsonRegExp: true }) // { _id: ObjectId, a: BSONRegExp { pattern: '(?-i)AA_', options: '' } } ``` Also there was an issue with `Cursor.forEach` where user defined forEach callbacks that throw errors incorrectly handled catching errors. Take a look at the comments in this example: ```javascript collection.find({}).forEach(doc => { if(doc.bad) throw new Error('bad document!'); }).catch(error => { // now this is called! and error is `bad document!` }) // before this fix the `bad document!` error would be thrown synchronously // and have to be caught with try catch out here ``` ##### Bug Fixes - **NODE-2035:** Exceptions thrown from awaited cursor forEach do not propagate ([#​2852](https://togithub.com/mongodb/node-mongodb-native/issues/2852)) ([a917dfa](https://togithub.com/mongodb/node-mongodb-native/commit/a917dfada67859412344ed238796cf3bee243f5f)) - **NODE-3150:** added bsonRegExp option for v3.6 ([#​2843](https://togithub.com/mongodb/node-mongodb-native/issues/2843)) ([e4a9a57](https://togithub.com/mongodb/node-mongodb-native/commit/e4a9a572427666fd1a89576dadf50b9c452e1659)) - **NODE-3358:** Command monitoring objects hold internal state references ([#​2858](https://togithub.com/mongodb/node-mongodb-native/issues/2858)) ([750760c](https://togithub.com/mongodb/node-mongodb-native/commit/750760c324ddedb72491befde9f7aff1ceec009c)) - **NODE-3380:** perform retryable write checks against server ([#​2861](https://togithub.com/mongodb/node-mongodb-native/issues/2861)) ([621677a](https://togithub.com/mongodb/node-mongodb-native/commit/621677a42772e0b26aa13883f57d7e42f86df43f)) - **NODE-3397:** report more helpful error with unsupported authMechanism in initial handshake ([#​2876](https://togithub.com/mongodb/node-mongodb-native/issues/2876)) ([3ce148d](https://togithub.com/mongodb/node-mongodb-native/commit/3ce148d8fb37faea1ee056f6e9331e5282e65cd0)) ##### Documentation - Reference: https://docs.mongodb.com/drivers/node/current/ - API: http://mongodb.github.io/node-mongodb-native/3.6/api - Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.6/HISTORY.md We invite you to try the mongodb package immediately, and report any issues to the [NODE project](https://jira.mongodb.org/projects/NODE).

Configuration

📅 Schedule: "before 7am on Tuesday" in timezone Australia/Sydney.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.



This PR has been generated by WhiteSource Renovate. View repository job log here.

changeset-bot[bot] commented 3 years ago

⚠️ No Changeset found

Latest commit: fec8a7cef2823031ca172ea6145b6290d376aa65

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR