[Security] Bump mongodb from 3.1.10 to 3.6.8

[dependabot-preview[bot]]

Bumps mongodb from 3.1.10 to 3.6.8. This update includes a security fix.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Denial of Service in mongodb Versions of mongodb prior to 3.1.13 are vulnerable to Denial of Service. The package fails to properly catch an exception when a collection name is invalid and the DB does not exist, crashing the application.

Recommendation

Upgrade to version 3.1.13 or later.

Affected versions: < 3.1.13

Release notes

Sourced from mongodb's releases.

v3.6.8

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

Release Highlights

Thanks to the quick adoption of the previous new patch by the mongoose package (Automattic/mongoose#10265) a small bug was identified when connections to mongodb would timeout causing unnecessary clean up operations to run. Thank you @​vkarpov15!

Bug Fixes

• NODE-3305: undo flipping of beforeHandshake flag for timeout errors (#2813) (6e3bab3)

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.

v3.6.7

The MongoDB Node.js team is pleased to announce version 3.6.7 of the driver

Release Highlights

This patch addresses a number of bug fixes. Notably, there was an interesting javascript related issue with sorting documents. It only impacts users using numerical keys in their documents.

> { a: 'asc', [23]: 'asc' }
{ [23]: 'asc', a: 'asc' } // numbers come first

In javascript, numerical keys are always iterated first when looping over the keys of an object followed by the chronological specification of each string key. This effectively changes the ordering of a sort document sent to mongodb. However our driver does accept sort specification in a variety of ways and one way to avoid this problem is passing an array of tuples:

[['a', 'asc'], ['23', 'asc']]

This ensures that mongodb is sent the 'a' key as the first sort key and '23' as the second.

Bug Fixes

• NODE-3159: removing incorrect apm docs (#2793) (971259a)
• NODE-3173: Preserve sort key order for numeric string keys (#2790) (730f43a)
• NODE-3176: handle errors from MessageStream (#2774) (f1afcc4)
• NODE-3192: check clusterTime is defined before access (#2806) (6ceace6)
• NODE-3252: state transistion from DISCONNECTED (#2807) (5d8f649)
• NODE-3219: topology no longer causes close event (#2791) (16e7064)
• invalid case on writeconcern makes skip check fail (#2773) (b1363c2)

Documentation

... (truncated)

Commits

• 6c8cc84 chore(release): 3.6.8
• 6e3bab3 fix(cmap): undo flipping of beforeHandshake flag for timeout errors (#2813)
• 4fd03e8 chore(release): 3.6.7
• 6ceace6 fix(NODE-3192): check clusterTime is defined before access (#2806)
• 1967515 test(NODE-3187): port unified test runner (#2783)
• 5d8f649 fix(NODE-3252): state transistion from DISCONNECTED (#2807)
• f916843 refactor(NODE-1812): Deprecate returnOriginal in favor of returnDocument (#2808)
• 945e915 refactor: deprecate remove, removeOne, insertMany bulk operations (#2797)
• be269b1 chore(NODE-3198): bump optional-require for yarn v2 pnp support (#2781)
• 730f43a fix(NODE-3173): Preserve sort key order for numeric string keys (#2790)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by nbbeeken, a new releaser for mongodb since your current version.

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 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) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #459.