codecov[bot]
commented
5 years ago Codecov Report
Merging #289 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #289 +/- ##
=======================================
Coverage 23.55% 23.55%
=======================================
Files 99 99
Lines 2165 2165
=======================================
Hits 510 510
Misses 1655 1655Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 7f73d5d...5ea7606. Read the comment docs.
dependabot-preview[bot]
Bumps mongodb from 3.1.13 to 3.3.1.
Release notes
*Sourced from [mongodb's releases](https://github.com/mongodb/node-mongodb-native/releases).* > ## v3.3.0 > The MongoDB Node.js team is pleased to announce version 3.3.0 of the driver > > ## Release Highlights > > ### Server Version 4.2 feature support > > This latest release brings support for features in the newly released [MongoDB v4.2](https://www.mongodb.com/blog/post/mongodb-42-is-now-ga-ready-for-your-production-apps): > > * Distributed Transactions > * On-Demand Materialized Views with the `$merge` operator > * Wildcard Indexes > * Retryable Reads > * MongoDB Query Language Enhancements. > > ### SRV Polling for Sharded Clusters > > The Driver has supported connecting to a cluster using an SRV record since version 3.0. Prior to now, we would only resolve the SRV record when initially connecting. This was fine for single replica sets, as the driver is able to discover new members added after initial connect from any member of a replica set. However, in a sharded deployment, individual mongos processes do not have an awareness of each other. This means that if the deployment changes in a shared cluster, the driver would have no way of knowing without disconnecting and connecting with a new client. > > Starting in 3.3, if a driver connects to a sharded cluster with an SRV record, we will now periodically check that SRV record for any changes in the deployment, and update the client-side connections accordingly. > > **NOTE: This feature is only available when starting a client with `{ useUnifiedTopology: true }` ** > > ### Beta support for MongoDB Client-Side Encryption > > The driver now has support for[ MongoDB Client-Side Encryption](https://docs.mongodb.com/manual/core/security-client-side-encryption). This requires installing the [`mongodb-client-encryption`](https://www.npmjs.com/package/mongodb-client-encryption) npm package in your project. > > ### Merged `mongodb-core` into `node-mongodb-native` > > Up until this release, the `mongodb` driver has consisted of two components: > > * `mongodb-core`: The low-level engine of the driver. > * `node-mongodb-native`: The API layer of the driver, published as `mongodb` > > Over time, this separation has done more harm than good, and has led to increased development time for repairing bugs and implementing new features. Starting in the 3.3 release of `mongodb`, we have merged `mongodb-core` into `node-mongodb-native`, removing this barrier to development. > > ## Release Notes > >Bug >
>>- [NODE-1480] - &[#39](https://github-redirect.dependabot.com/mongodb/node-mongodb-native/issues/39);Should handle Error thrown during operation&[#39](https://github-redirect.dependabot.com/mongodb/node-mongodb-native/issues/39); in error_tests.js should handle exception
>
> - [NODE-1994] - fix &[#39](https://github-redirect.dependabot.com/mongodb/node-mongodb-native/issues/39);should correctly handle multiple unordered batch API&[#39](https://github-redirect.dependabot.com/mongodb/node-mongodb-native/issues/39);
>
> - [NODE-2022] - startAtOperationTime and resumeToken conflict on cursor restarts
>
> - [NODE-2051] - MongoClient with autoEncryption does not clean up MongoCryptD client
>
> - [NODE-2054] - [FLE] AutoEncrypter MongoClient does not use new url parser
> ... (truncated)
Changelog
*Sourced from [mongodb's changelog](https://github.com/mongodb/node-mongodb-native/blob/master/HISTORY.md).* > # Change Log > > All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines. > > > ## [3.2.7](https://github.com/mongodb/node-mongodb-native/compare/v3.2.6...v3.2.7) (2019-06-04) > > > ### Bug Fixes > > * **core:** updating core to version 3.2.7 ([2f91466](https://github.com/mongodb/node-mongodb-native/commit/2f91466)) > * **findOneAndReplace:** throw error if atomic operators provided for findOneAndReplace ([6a860a3](https://github.com/mongodb/node-mongodb-native/commit/6a860a3)) > > > > > ## [3.2.6](https://github.com/mongodb/node-mongodb-native/compare/v3.2.5...v3.2.6) (2019-05-24) > > > > > ## [3.2.5](https://github.com/mongodb/node-mongodb-native/compare/v3.2.4...v3.2.5) (2019-05-17) > > > ### Bug Fixes > > * **core:** updating core to 3.2.5 ([a2766c1](https://github.com/mongodb/node-mongodb-native/commit/a2766c1)) > > > > > ## [3.2.4](https://github.com/mongodb/node-mongodb-native/compare/v3.2.2...v3.2.4) (2019-05-08) > > > ### Bug Fixes > > * **aggregation:** fix field name typo ([4235d04](https://github.com/mongodb/node-mongodb-native/commit/4235d04)) > * **async:** rewrote asyncGenerator in node < 10 syntax ([49c8cef](https://github.com/mongodb/node-mongodb-native/commit/49c8cef)) > * **BulkOp:** run unordered bulk ops in serial ([f548bd7](https://github.com/mongodb/node-mongodb-native/commit/f548bd7)) > * **bulkWrite:** fix issue with bulkWrite continuing w/ callback ([2a4a42c](https://github.com/mongodb/node-mongodb-native/commit/2a4a42c)) > * **docs:** correctly document that default for `sslValidate` is false ([1f8e7fa](https://github.com/mongodb/node-mongodb-native/commit/1f8e7fa)) > * **gridfs-stream:** honor chunk size ([9eeb114](https://github.com/mongodb/node-mongodb-native/commit/9eeb114)) > * **unified-topology:** only clone pool size if provided ([8dc2416](https://github.com/mongodb/node-mongodb-native/commit/8dc2416)) > > > ### Features > > * update to mongodb-core v3.2.3 ([1c5357a](https://github.com/mongodb/node-mongodb-native/commit/1c5357a)) > * **core:** update to mongodb-core v3.2.4 ([2059260](https://github.com/mongodb/node-mongodb-native/commit/2059260)) > * **lib:** implement executeOperationV2 ([67d4edf](https://github.com/mongodb/node-mongodb-native/commit/67d4edf)) > ... (truncated)Commits
- See full diff in [compare view](https://github.com/mongodb/node-mongodb-native/commits)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 will not automatically merge this PR because it includes a minor update to a production dependency.
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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.