Bump mongodb from 3.6.2 to 3.6.5 in /server

[dependabot]

Bumps mongodb from 3.6.2 to 3.6.5.

Release notes

Sourced from mongodb's releases.

v3.6.5

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

Notable Fixes

In this patch there is a fix surrounding an issue some users were encountering in serverless environments when using the Unified Topology. If the nodejs process went unused for a great amount of time there was an intermittent issue that would cause startSession to fail, however, issuing a dummy read request would resolve the problem. The session support check is now done after server selection meaning the driver has the most up to date information about the MongoDB deployment before utilizing sessions. We encourage any user's that implemented workarounds to updated their driver and make use of this fix.

In addition, the previous release of our driver added a warning about an upcoming change in the v4 version of the driver about how users can specify their write concern options. We've updated the driver to use nodejs's process.emitWarning API in nearly all cases where the driver prints something out, as well as limit most warning messages to only be printed once.

Bug

• session support detection spec compliance (#2732) (9baec71)
• [NODE-3100] - startSession fails intermittently on servers that support sessions
• [NODE-3066] - Accessing non-existent property 'MongoError' of module exports inside circular dependency
• [NODE-3114] - Incorrect warning: Top-level use of w, wtimeout, j, and fsync is deprecated
• [NODE-3119] - Node 14.5.4, mongo 3.6.4 Circular warnings

v3.6.4

MongoDB Driver v3.6.4

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

Release Highlights

Explain Support

The full set of $explain verbosity settings are now supported:

• queryPlanner
• queryPlannerExtended
• executionStats
• allPlansExecution

In the following commands:

• aggregate() (MDB 3.0+)
• find() (MDB 3.0+)
• remove() (MDB 3.0+)
• update() (MDB 3.0+)
• distinct() (MDB 3.2+)
• findAndModify() (MDB 3.2+)
• mapReduce() (MDB 4.4+)

You can get a lot of insight into the performance of a query or optimization using these fine grained reports. To learn more about how to use explain read here.

Direct Connection Issue Revert

We removed automatic direct connection for the unified topology in the 3.6.3 release of the driver. This change was preparatory for the 4.0 version of the driver, where we'll always perform automatic discovery. To avoid making this kind of change in a patch release, this version restores automatic direct connection when connecting to a single host using the unified topology without a specified replicaSet and without directConnection: false, in line with previous 3.6 releases.

... (truncated)

Commits

• 6887e8d chore(release): 3.6.5
• 8b370a7 fix: move session support check to operation layer (#2739)
• 2d76492 chore: boron node version test failures (#2747)
• 8bd9777 fix: use emitWarning API for internal messages (#2743)
• d67ffa7 fix: MongoError circular dependency warning (#2734)
• 9baec71 fix: session support detection spec compliance (#2732)
• e8ac558 test: restrict destroy test to versions of node that support it (#2728)
• db1ab0b chore: format readme and add note about 4.0 beta (#2729)
• a485346 chore(release): 3.6.4
• 2fffb52 test: Adding test for cursor cloning removing session (#2723)
• 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)

[vercel]

Deployment failed with the following error:

The most recent charge for your active payment method has failed. Please update it here: https://vercel.com/teams/lnteluon/settings/billing.

[dependabot]

Superseded by #213.