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