[Snyk] Upgrade mongodb from 3.6.3 to 3.6.5

[snyk-bot]

Snyk has created this PR to upgrade mongodb from 3.6.3 to 3.6.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 2 versions ahead of your current version.
• The recommended version was released 22 days ago, on 2021-03-16.

Release notes

Package name: mongodb

• 3.6.5 - 2021-03-16
  

  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
• 3.6.4 - 2021-02-02
  

  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.

  NOTE: In the next major version the unifiedTopology is the only Topology and it is required to either specify a replicaSet name or enable directConnection in order to connect to single nodes in a replica set.

  Support Azure and GCP keystores in FLE

  There are no functional changes to the driver to support using Azure and GCP keystores but a new mongodb-client-encryption release (v1.2.0) can be found here which prominently features support for these key stores.

  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!

  Release Notes

  Bug

  • [NODE-2355] - GridFSBucketWriteStream doesn't implement stream.Writable properly
  • [NODE-2828] - noCursorTimeout does not seem to for find()
  • [NODE-2874] - Setting connectionTimeoutMS to 0 will result in a disconnection every heartbeatFrequencyMS
  • [NODE-2876] - Race condition when resetting server monitor
  • [NODE-2916] - Legacy topology hangs with unlimited socket timeout
  • [NODE-2945] - ignoreUndefined not works on findOneAndUpdate when { upsert: true }
  • [NODE-2965] - MongoClient.readPreference returns "primary" ignoring readPref from connection string
  • [NODE-2966] - Unified topology: server selection fails when trying to connect to a remote replica set with a member whose 'host' attribute resolves to 'localhost'
  • [NODE-2977] - Query parameters with path in connection string not working on windows
  • [NODE-2986] - MongoError: pool destroyed

  Features

  • [NODE-2762] - Comprehensive Support for Explain
  • [NODE-2852] - Add explain support to non-cursor commands
  • [NODE-2853] - Add explain support to cursor-based commands

  Improvement

  • [NODE-1726] - Deprecate Topology events in Db
  • [NODE-2825] - Support Azure and GCP keystores in FLE
  • [NODE-2880] - Improve stack traces in the session leak checker
  • [NODE-2895] - Update AggregateCursor "unwind" method to match the native driver
  • [NODE-2995] - Sharing a MongoClient for metadata lookup can lead to deadlock in drivers using automatic encryption
• 3.6.3 - 2020-11-06
  

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

  Release Highlights

  MongoError: not master when running createIndex

  A regression introduced in v3.6.2 meant that createIndex operations would not be executed with a fixed
  primary read preference. This resulted in the driver selecting any server for the operation, which would
  fail if a non-primary was selected.

  Performance issues on AWS Lambda

  The driver periodically monitors members of the replicaset for changes in the topology, but ensures that
  the "monitoring thread" is never woken sooner than 500ms. Measuring this elapsed time depends on a
  stable clock, which is not available to us in some virtualized environments like AWS Lambda. The result
  was that periodically operations would think there were no available servers, and the driver would force
  a wait of heartbeatFrequencyMS (10s by default) before reaching out to servers again for a new
  monitoring check. The internal async interval timer has been improved to account for these environments

  GSSAPI AuthProvider reuses single kerberos client

  A regression introduced in v3.6.0 forced the driver to reuse a single kerberos client for all
  authentication attempts. This would result in incomplete authentication flows, and occaisionally even
  a crash in the kerberos module. The driver has been reverted to creating a kerberos client per
  authentication attempt.

  Performance regression due to use of setImmediate

  A change introduced in v3.6.1 switched all our usage of process.nextTick in the connection pool with
  setImmediate per Node.js core recommendation. This was observed to introduce noticeable latency when the event loop
  was experiencing pressure, so the change was reverted for this release pending further investigation.

  Community Contributions

  • @ jswangjunsheng submitted a fix for a rare scenario when wait queue members time out before connection establishment
  • @ through-a-haze submitted a fix for incorrect construction of an X509 authentication message
  • @ andreialecu helped us indicate peer optional dependencies in our package.json for stricter package managers (pnpm, yarn2)

  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!

  Release Notes

  Bug

  • [NODE-2172] - Change stream breaks on disconnection when there's something piped into it.
  • [NODE-2784] - MongoError: Not Master when running createIndex in 3.6.0
  • [NODE-2807] - MongoClient.readPreference always returns primary
  • [NODE-2827] - Connecting to single mongos makes driver think it is connected to a standalone
  • [NODE-2829] - MongoDB Driver 3.6+ Performance issues on AWS Lambda
  • [NODE-2835] - Remove default timeout for read operations
  • [NODE-2859] - GSSAPI AuthProvider causing crashes in Compass
  • [NODE-2861] - Performance Regression for usage of mongodb connections (queries, inserts, ...)
  • [NODE-2865] - Connections can be leaked if wait queue members are cancelled
  • [NODE-2869] - Invalid assignment of X509 username makes authentication impossible

  Improvement

  • [NODE-2834] - Remove deprecation of AggregationCursor#geoNear
  • [NODE-2867] - Use peerDependenciesMeta field to mark peer optional dependencies

from mongodb GitHub release notes

Commit messages

Package name: mongodb

• 6887e8d chore(release): 3.6.5
• 8b370a7 fix: move session support check to operation layer (Makes sure we plumb auth.installationId when updating installations #2739)
• 2d76492 chore: boron node version test failures (Makes sure pointer includes are interpolated as get #2747)
• 8bd9777 fix: use emitWarning API for internal messages (Unable to download file from the parse-server #2743)
• d67ffa7 fix: MongoError circular dependency warning (Specify password requirements on password reset #2734)
• 9baec71 fix: session support detection spec compliance (Lookup for email in username field to match docs if email is undefined #2732)
• e8ac558 test: restrict destroy test to versions of node that support it (Use lodash implementations instead of polyfills for .values and .entries #2728)
• db1ab0b chore: format readme and add note about 4.0 beta (Revert "Removes runtime dependency babel-polyfill" #2729)
• a485346 chore(release): 3.6.4
• 2fffb52 test: Adding test for cursor cloning removing session (Adds exporting vars after success #2723)
• 6314f5a chore(ci): fix aws auth tests (handleUpdateToRevocableSession cause HTTP 500 error #2720)
• 617d9de fix: restore auto direct connection behavior (Update jasmine to version 2.5.2 🚀 #2719)
• 8082c89 fix(cursor): don't use other operation's session for cloned cursor operation ( Saved filename fixed so that clients display it correctly #2415 #2705)
• f89e4c1 fix: dont parse tls/ssl file paths in uri (Parse issue in Swift 3 #2718)
• b657c8c fix: respect readPreference and writeConcern from connection string (Json parser seems to be eating up a lot of response time #2711)
• b5e9d67 fix: Allow GridFS write stream to destroy (Cross Domain Issue #2702)
• e257e6b fix(find): correctly translate timeout option into noCursorTimeout (Session token without expiry date #2700)
• 60936dc fix: hasAtomicOperator check respects toBSON transformation (parse server push only sent to part of the audience #2696)
• 7e89e47 test: add tests for azure and GCP CSFLE (Adds more expressive schema mismatch errors #2662)
• 8daff7f chore: Remove unused CI files (Revert "Tries a new travis configuration" #2684)
• f557c8a chore(ci): continuous matrix integration [3.6] (Crash if logout is made to not existing user #2667)
• a25b67c fix: honor ignoreUndefined on findAndModify commands (Parse server not uploading file > 1mb, logs in server: "client intended to send too large body" #2671)
• db3f800 docs: fix type for aggregation cursor unwind param (Add NullCacheAdapter #2636)
• cdb614d test: write concern command construction test cleanup (Parse.FacebookUtils.isLinked(user) returns false since parse-server 2.2.6 #2342)

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[codecov]

Codecov Report

Merging #7322 (a2c6417) into master (c56d326) will decrease coverage by 0.01%.
The diff coverage is n/a.

❗ Current head a2c6417 differs from pull request most recent head aa20eb4. Consider uploading reports for the commit aa20eb4 to get more accurate results

@@            Coverage Diff             @@
##           master    #7322      +/-   ##
==========================================
- Coverage   93.91%   93.89%   -0.02%     
==========================================
  Files         181      181              
  Lines       13194    13194              
==========================================
- Hits        12391    12389       -2     
- Misses        803      805       +2     

Impacted Files	Coverage Δ
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	92.59% <0.00%> (-0.66%)	⬇️
src/RestWrite.js	93.92% <0.00%> (-0.16%)	⬇️
src/batch.js	93.10% <0.00%> (+1.72%)	⬆️
src/Adapters/Auth/httpsRequest.js	100.00% <0.00%> (+4.76%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c56d326...aa20eb4. Read the comment docs.

[parseplatformorg]

🎉 This change has been released in version 5.0.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 5.0.0