Bump mongodb from 2.2.36 to 3.6.7

[dependabot]

Bumps mongodb from 2.2.36 to 3.6.7.

Release notes

Sourced from mongodb's releases.

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

• Reference: http://mongodb.github.io/node-mongodb-native/3.6
• 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 driver immediately, and report any issues to the NODE project.

Thanks very much to all the community members who contributed to this release!

v3.6.6

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

Release Highlights

This patch addresses a number of bugs listed below. Most notably, for client side encryption users upgrading to this version of the driver along with the new version of mongodb-client-encryption@1.2.3 will alleviate the potential deadlock case if your connection pool was fully utilized. There will now be an internal MongoClient that will be used for metadata look ups (e.g, listCollections) when the pool size is under certain constraints. The events generated from this client are forwarded to the client instance you initialize so it is possible to monitor all events.

Bug

... (truncated)

Commits

• 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)
• 16e7064 fix(sdam): topology no longer causes close event (#2791)
• 971259a fix(docs): removing incorrect apm docs (#2793)
• 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]

Superseded by #26.