fix(deps): update all (major)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
async (source)	dependencies	major	^2.6.1 -> ^3.0.0
ejs	dependencies	major	^2.6.1 -> ^3.0.0
mongodb	dependencies	major	^2.2.36 -> ^3.0.0

---

Release Notes

caolan/async

v3.2.0

Compare Source

• Fix a bug in Safari related to overwriting func.name
• Remove built-in browserify configuration (#​1653)
• Varios doc fixes (#​1688, #​1703, #​1704)

v3.1.1

Compare Source

• Allow redefining name property on wrapped functions.

v3.1.0

Compare Source

• Added q.pushAsync and q.unshiftAsync, analagous to q.push and q.unshift, except they always do not accept a callback, and reject if processing the task errors. (#​1659)
• Promises returned from q.push and q.unshift when a callback is not passed now resolve even if an error ocurred. (#​1659)
• Fixed a parsing bug in autoInject with complicated function bodies (#​1663)
• Added ES6+ configuration for Browserify bundlers (#​1653)
• Various doc fixes (#​1664, #​1658, #​1665, #​1652)

v3.0.1

Compare Source

Bug fixes

• Fixed a regression where arrays passed to queue and cargo would be completely flattened. (#​1645)
• Clarified Async's browser support (#​1643)

v3.0.0

Compare Source

The async/await release!

There are a lot of new features and subtle breaking changes in this major version, but the biggest feature is that most Async methods return a Promise if you omit the callback, meaning you can await them from within an async function.

const results = await async.mapLimit(urls, 5, async url => {
    const resp = await fetch(url)
    return resp.body
})

Breaking Changes

• Most Async methods return a Promise when the final callback is omitted, making them await-able! (#​1572)
• We are now making heavy use of ES2015 features, this means we have dropped out-of-the-box support for Node 4 and earlier, and many old versions of browsers. (#​1541, #​1553)
• In queue, priorityQueue, cargo and cargoQueue, the "event"-style methods, like q.drain and q.saturated are now methods that register a callback, rather than properties you assign a callback to. They are now of the form q.drain(callback). If you do not pass a callback a Promise will be returned for the next occurrence of the event, making them await-able, e.g. await q.drain(). (#​1586, #​1641)
• Calling callback(false) will cancel an async method, preventing further iteration and callback calls. This is useful for preventing memory leaks when you break out of an async flow by calling an outer callback. (#​1064, #​1542)
• during and doDuring have been removed, and instead whilst, doWhilst, until and doUntil now have asynchronous test functions. (#​850, #​1557)
• limits of less than 1 now cause an error to be thrown in queues and collection methods. (#​1249, #​1552)
• memoize no longer memoizes errors (#​1465, #​1466)
• applyEach/applyEachSeries have a simpler interface, to make them more easily type-able. It always returns a function that takes in a single callback argument. If that callback is omitted, a promise is returned, making it awaitable. (#​1228, #​1640)

New Features

• Async generators are now supported in all the Collection methods. (#​1560)
• Added cargoQueue, a queue with both concurrency and payload size parameters. (#​1567)
• Queue objects returned from queue now have a Symbol.iterator method, meaning they can be iterated over to inspect the current list of items in the queue. (#​1459, #​1556)
• A ESM-flavored async.mjs is included in the async package. This is described in the package.json "module" field, meaning it should be automatically used by Webpack and other compatible bundlers.

Bug fixes

• Better handle arbitrary error objects in asyncify (#​1568, #​1569)

Other

• Removed Lodash as a dependency (#​1283, #​1528)
• Miscellaneous docs fixes (#​1393, #​1501, #​1540, #​1543, #​1558, #​1563, #​1564, #​1579, #​1581)
• Miscellaneous test fixes (#​1538)

---

mde/ejs

v3.1.3

Compare Source

v3.1.2

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

• Removed require.extensions (@​mde)
  • Removed legacy preprocessor include (@​mde)
  • Removed support for EOL Nodes 4 and 6 (@​mde)

mongodb/node-mongodb-native

v3.5.9

Compare Source

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

Release Highlights

Use duration of handshake if no previous roundTripTime exists

The default roundTripTime of a ServerDescription is -1, which means if that value is used we can potentially calculate a negative roundTripTime. Instead, if no previous roundTripTime exists, we use the duration of the initial handshake.

the options [maxIdleTimeMS] is not supported

A number of new options were added when the CMAP compliant connection pool was introduced in 3.5.x. Unfortunately, these options were not documented properly. Now they are mentioned in the MongoClient documentation, with a notice that they are only supported with the unified topology.

TypeError: Reduce of empty array with no initial value

A fix in 3.5.8 which ensured proper filtering of servers during server selection exposed an issue in max staleness calculations when the topology type is ReplicaSetNoPrimary and no servers are currently known. In order to estimate an upper bound of max staleness when there is no primary, the most stale known server is known to compare the others to - if there are no known servers, you can't reduce the array!

Server monitoring is prevented under heavy request load

In certain very high load fail-over scenarios the driver is unable to reschedule a monitoring check in order to update its view of the topology for retryability. This would result in a high number of failed operations, as they were unable to determine a new viable server.

Documentation

Reference: http://mongodb.github.io/node-mongodb-native/3.5/
API: http://mongodb.github.io/node-mongodb-native/3.5/api/
Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.5/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-2637] - connection pool options support for MongoClient
• [NODE-2641] - maxStalenessReducer fails on empty set of servers
• [NODE-2643] - Server monitoring is prevented under heavy request load
• [NODE-2652] - Use duration of initial handshake if no roundTripTime value exists for server

Improvement

• [NODE-2651] - Use consistent means of measuring time

v3.5.8

Compare Source

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

Release Highlights

Fixes for NEAREST latency window calculation

@​adityapatadia helped uncover an issue with our server selection logic which
filtered out servers after evaluating whether they were in the latency window.
This meant that non-viable servers were considered during the window calculation
and would render certain viable servers unviable.

BulkWriteError writeErrors property

@​vkarpov15 submitted a patch to always include writeErrors on a BulkWriteError.
We have logic to set the message of BulkWriteError to the message of the first
error encountered if there is only one error. Unfortunately, this logic removed
the writeErrors field when doing that, so users could be faced with an error
which conditionally changed shape.

Memory leak in timed out wait queue members

@​dead-horse identified a memory leak in the new connection pool where wait queue
members which timed out might be left in the queue indefinitely under sufficient
load. The fix here was to ensure that all wait queue members are flushed during
wait queue processing before evaluating whether there were available sockets to
process new requests.

Implicit sessions cleanup improvements

Once @​dead-horse was able to patch the connection pool memory leak, they also
identified a edge case where implicit sessions could be leaked in a very specific
error condition. The logic to release implicit sessions was simplified, preventing
this from happening in the future

Unordered bulk writes continue-on-error

A bug introduced last summer prevented unordered bulk write operations from
continuing after the first write error - one of the most important features of
being an unordered operation. We now properly support this feature again.

journal in connection string is ignored

@​nknighter filed a report that the journal option was ignored when provided
via the connection string. The paramater j was supported both through the
connection string and explicit added to MongoClient options, but the official
documentation for connection strings support a journal option.

Documentation

Reference: http://mongodb.github.io/node-mongodb-native/3.5/
API: http://mongodb.github.io/node-mongodb-native/3.5/api/
Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.5/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-2407] - UnifiedTopology + near read makes application crash with timeout error when one of replica server is down
• [NODE-2413] - The node process enters an infinite loop at the pool and causes OOM
• [NODE-2442] - journal=true is ignored in connection string
• [NODE-2548] - Change streams do not resume from errors
• [NODE-2565] - Change stream should not check for NonResumableChangeStreamError label
• [NODE-2619] - Unordered bulk write aborts on first encountered error
• [NODE-2625] - BulkWriteError should always have a writeErrors field

Task

• [NODE-2478] - Use white list for change stream resumability
• [NODE-2598] - Change stream close refactor
• [NODE-2605] - Refactor shared test helpers to improve usability

Improvement

• [NODE-2522] - Remove ElectionInProgress (216) from ResumableChangeStreamError
• [NODE-2571] - Don&#​39;t use admin database for FLE tests
• [NODE-2630] - Simplify code path for ending implicit sessions in cursors

v3.5.7

Compare Source

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

Release Highlights

Warning: Accessing non-existent property 'count' of module exports inside circular dependency

Work earlier this year left some dead code in our operations code, resulting in this warning message reported by multiple users. While we still have a few cycles in our codebase yet, this will quiet Node.js 14's circular dependency warnings.

Sessions are only acquired when operations are executed

Drivers use an implicit session for all operations where an explicit session is not provided. A subtle bug was introduced when session support was implemented where implicit sessions were created and assigned to operations even if they were about to sit in a queue waiting for execution. This results in the driver creating many sessions rather than reusing pooled ones. The fix is to ensure a session is only checked out of the pool when the operation is about to be written to a server.

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

Release Notes

Bug

• [NODE-2536] - Circular dependency in Node.js 14 nightly
• [NODE-2552] - Server session creation grows unbounded with every operation call

Improvement

• [NODE-2534] - Document options supported by the unified topology
• [NODE-2560] - Make &#​39;reIndex&#​39; a standalone-only command

v3.5.6

Compare Source

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

Release Highlights

Regression in map when cursor used as a stream

@​dobesv helped identify a regression where a map function would be applied twice
if defined on a cursor, and that cursor was used to stream data.

TypeError: Cannot read property 'code' of undefined

User @​linus-hologram originally reported an issue with a TypeError when the lambda
passed to the withTransaction helper rejected with a null value. @​vkarpov15
submitted the fix.

readPreferenceTags interpreted as an array

A bug was fixed where readPreferenceTags with a single value in the connection
string was not properly interpreted as an array of tags. This prevented the
Use Analytics Nodes to Isolate Workload guidance from working
correctly.

Cannot set property 'isDirty' of null

User @​sean-daley reported seeing this in an AWS Lambda environment, but has proven to
be somewhat of a heisenbug. We are rolling out a fix here that ensures sessions
(implicit or not) are not used after they have been explicitly ended.

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

Release Notes

Bug

• [NODE-2503] - Cursor ReadStream applies map function twice
• [NODE-2515] - TypeError when transaction is rejected with empty reason
• [NODE-2541] - readPreferenceTags are not interpreted as an array
• [NODE-2545] - Cannot set property &#​39;isDirty&#​39; of null
• [NODE-2549] - Unknown topology should return empty array for server selection with read preference

v3.5.5

Compare Source

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

Release Highlights

Regression in hasNext when using a cursor with a limit

@​peterbroadhurst helped point out a regression introduced in v3.5.4 where using hasNext
on a cusor with a limit would not return the full set of results.

Ignored topology updates cause servers to fall out of latency window

A change introduced across all MongoDB drivers, and in particular v3.5.0 of the Node.js
driver, attempted to prevent needless duplicate topologyDescriptionChanged topology events
by introducing a ServerDescription equality operator. Since equality does not take the
lastUpdateTime and lastWriteDate fields of an ismaster into account, the driver could
eventually consider servers non-suitable for server selection, since they would fall out
of the latency window.
All updates are considered viable for topology updates now, and only event emission is
gated by ServerDescription equality.

Memory leaks with Node.js v12+

The legacy topology types (in particular if you were connected to a replic set) used a
custom Timeout class to wrap a timer. Unfortunately, the class depended on an undocumented,
private variable _called, which was removed in Node.js v12. This would lead to the driver
thinking the timeout never occurred, and therefore never releasing the object for garbage
collection. We recommend users of the legacy topology types immediately update to this
version of the driver, or use the Unified Topology which is unaffected by this bug.

TypeError: Cannot read property 'Symbol(cancelled)' of undefined

@​erfanium and @​Paic helped us identify an issue in rare failover events where multiple
requests to process the server selection queue would result in an attempted property
access of an undefined variable.

promiseLibrary not respected by newly introduced maybePromise helper

@​tobyealden pointed out that an internal refactor to use a helper to optionally
return a Promise for top level API methods was not, in fact, using a custom
promise library if one was provided!

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

Release Notes

Bug

• [NODE-2460] - Memory Leak with ReplSet and NodeJS v12
• [NODE-2472] - TypeError on server available with useUnifiedTopology: true
• [NODE-2474] - Server_Description update with lastUpdateTime / lastWriteDate fields is ignored in topology
• [NODE-2480] - TypeError after reconnecting
• [NODE-2483] - Regression using hasNext on cursor with limit
• [NODE-2490] - promiseLibrary option is not honoured

v3.5.4

Compare Source

Bug Fixes

• cmap: don't run min connection thread if no minimum specified (2d1b713)
• sdam: use ObjectId comparison to track maxElectionId (a1e0849)
• topology: ensure selection wait queue is always processed (bf701d6)
• topology: enter STATE_CLOSING before draining waitQueue (494dffb)
• don't consume first document when calling hasNext on cursor (bb359a1)

Features

• add utility helper for returning promises or using callbacks (ac9e4c9)

v3.5.3

Compare Source

Bug Fixes

• message-stream: support multiple inbound message packets (8388443)
• server: non-timeout network errors transition to Unknown state (fa4b01b)

Features

• connection: support exhaust behavior at the transport level (9ccf268)

v3.5.2

Compare Source

Bug Fixes

• properly handle err messages in MongoDB 2.6 servers (0f4ab38)
• topology: always emit SDAM unrecoverable errors (57f158f)

v3.5.1

Compare Source

Bug Fixes

• cmap: accept all node TLS options as pool options (5995d1d)
• cmap: error wait queue members on failed connection creation (d13b153)
• connect: listen to secureConnect for tls connections (f8bdb8d)
• transactions: use options helper to resolve read preference (9698a76)
• uri_parser: TLS uri variants imply ssl=true (c8d182e)

v3.5.0

Compare Source

Bug Fixes

• copy ssl option to pool connection options (563ced6)
• destroy connections marked as closed on checkIn / checkOut (2bd17a6)
• ensure sync errors are thrown, and don't callback twice (cca5b49)
• ignore connection errors during pool destruction (b8805dc)
• not all message payloads are arrays of Buffer (e4df5f4)
• recover on network error during initial connect (a13dc68)
• remove servers with me mismatch in updateRsFromPrimary (95a772e)
• report the correct platform in client metadata (35d0274)
• reschedule monitoring before emitting heartbeat events (7fcbeb5)
• socket timeout for handshake should be connectTimeoutMS (c83af9a)
• timed out streams should be destroyed on timeout event (5319ff9)
• use remote address for stream identifier (f13c20b)
• used weighted RTT calculation for server selection (d446be5)
• execute-operation: don't swallow synchronous errors (0a2d4e9)
• gridfs: make a copy of chunk before writing to server (b4ec5b8)

Features

• add a withConnection helper to the connection pool (d59dced)
• include connectionId for APM with new CMAP connection pool (9bd360c)
• integrate CMAP connection pool into unified topology (9dd3939)
• introduce MongoServerSelectionError (0cf7ec9)
• introduce a class for tracking stream specific attributes (f6bf82c)
• introduce a new Monitor type for server monitoring (2bfe2a1)
• relay all CMAP events to MongoClient (1aea4de)
• support socket timeouts on a per-connection level (93e8ad0)

3.4.1 (2019-12-19)

Bug Fixes

• bulk: use original indexes as map for current op index (20800ac)
• always check for network errors during SCRAM conversation (e46a70e)

v3.4.1

Compare Source

Bug Fixes

• bulk: use original indexes as map for current op index (20800ac)
• always check for network errors during SCRAM conversation (e46a70e)

v3.4.0

Compare Source

Bug Fixes

• bulk: use operation index from input to report operation error (f713b13)
• command: only add TransientTransactionError label when in a transaction (478d714)
• compression: recalculate opcode after determine OP_COMPRESSED (022f51b)
• connect: connect with family 0 instead of family 4 (db07366)
• connection: timed out connections should not be half closed (850f4f5)
• cursor: call initialize after session support check (e50c51a)
• encryption: autoEncryption must error on mongodb < 4.2 (c274615)
• encryption: do not attempt to merge autoEncryption options (e27fdf9)
• encryption: encryption uses smaller batch size (cb78e69)
• encryption: respect bypassAutoEncryption (e927499)
• encryption: respect user bson options when using autoEncryption (cb7a3f7)
• add calculated duration to server as roundTripTime (cb107a8)
• mongodb+srv: respect overriding SRV-provided properties (ea83360)
• pool: flush workItems after next tick to avoid dupe selection (3ec49e5)
• pool: support a drain event for use with unified topology (da931ea)
• scram: verify server digest, ensuring mutual authentication (806cd62)
• srv-poller: always provide a valid number for intervalMS (afb125f)
• topology: correct logic for checking for sessions support (8d157c8)
• topology: don't drain iteration timers on server selection (fed6a57)

Features

• add MessageStream for streamed wire protocol messaging (8c44044)
• introduce a modern Connection replacement for CMAP (7890e48)
• support connection establishment cancellation (2014b7b)
• support driver info for drivers wrapping the node driver (1b6670b)

3.3.5 (2019-11-26)

Bug Fixes

• bulk: use operation index from input to report operation error (08ee53e)
• command: only add TransientTransactionError label when in a transaction (8bab074)
• connect: connect with family 0 instead of family 4 (7a41279)
• cursor: call initialize after session support check (3b076b3)
• mongodb+srv: respect overriding SRV-provided properties (5ed4c07)
• pool: support a drain event for use with unified topology (3471c28)
• topology: correct logic for checking for sessions support (2d976bd)
• topology: don't drain iteration timers on server selection (261f1e5)

Features

• support driver info for drivers wrapping the node driver (d85c4a8)

3.3.4 (2019-11-11)

Bug Fixes

• close: the unified topology emits a close event on close now (ee0db01)
• connect: prevent multiple callbacks in error scenarios (5f6a787)
• monitoring: incorrect states used to determine rescheduling (ec1e04c)
• pool: don't reset a pool if we'not already connected (32316e4)
• pool: only transition to DISCONNECTED if reconnect enabled (43d461e)
• replset: don't leak servers failing to connect (f209160)
• replset: use correct topologyId for event emission (19549ff)
• sdam: minHeartbeatIntervalMS => minHeartbeatFrequencyMS (af9fb45)
• sdam: don't emit close every time a child server closes (818055a)
• sdam: don't lose servers when they fail monitoring (8a534bb)
• sdam: don't remove unknown servers in topology updates (1147ebf)
• sdam: ignore server errors when closing/closed (49d7235)
• server: don't emit error in connect if closing/closed (62ada2a)
• server: ensure state is transitioned to closed on connect fail (a471707)
• topology: report unified topology as nodejs (d126665)
• topology: set max listeners to infinity for db event relay (edb1335)

Features

• sdam_viz: add new tool for visualizing driver sdam changes (738189a)
• sdam_viz: support legacy topologies in sdam_viz tool (1a5537e)
• update-hints: add support for hint to all update methods (720f5e5)

3.3.3 (2019-10-16)

Bug Fixes

• change_stream: emit 'close' event if reconnecting failed (f24c084)
• ChangeStream: remove startAtOperationTime once we have resumeToken (362afd8)
• connect: Switch new Buffer(size) -> Buffer.alloc(size) (da90c3a)
• MongoClient: only check own properties for valid options (9cde4b9)
• mongos: disconnect proxies which are not mongos instances (ee53983)
• mongos: force close servers during reconnect flow (186263f)
• monitoring: correct spelling mistake for heartbeat event (21aa117)
• replset: correct server leak on initial connect (da39d1e)
• replset: destroy primary before removing from replsetstate (45ac09a)
• replset: destroy servers that are removed during SDAM flow (9ea0190)
• saslprep: add in missing saslprep dependency (41f1165)
• topology: don't early abort server selection on network errors (2b6a359)
• topology: don't emit server closed event on network error (194dcf0)
• topology: include all BSON types in ctor for bson-ext support (aa4c832)
• topology: respect the force parameter for topology close (d6e8936)

Features

• Update: add the ability to specify a pipeline to an update command (#​2017) (44a4110)
• urlParser: default useNewUrlParser to true (52d76e3)

3.2.7 (2019-06-04)

Bug Fixes

• core: updating core to version 3.2.7 (2f91466)
• findOneAndReplace: throw error if atomic operators provided for findOneAndReplace (6a860a3)

3.3.2 (2019-08-28)

Bug Fixes

• change-stream: default to server default batch size (b3ae4c5)
• execute-operation: return promise on session support check (a976c14)
• gridfs-stream: ensure close is emitted after last chunk (ae94cb9)

3.3.1 (2019-08-23)

Bug Fixes

• find: respect client-level provided read preference (fec4f15)
• correct inverted defaults for unified topology (cf598e1)

v3.3.5

Compare Source

Bug Fixes

• bulk: use operation index from input to report operation error (08ee53e)
• command: only add TransientTransactionError label when in a transaction (8bab074)
• connect: connect with family 0 instead of family 4 (7a41279)
• cursor: call initialize after session support check (3b076b3)
• mongodb+srv: respect overriding SRV-provided properties (5ed4c07)
• pool: support a drain event for use with unified topology (3471c28)
• topology: correct logic for checking for sessions support (2d976bd)
• topology: don't drain iteration timers on server selection (261f1e5)

Features

• support driver info for drivers wrapping the node driver (d85c4a8)

v3.3.4

Compare Source

Bug Fixes

• close: the unified topology emits a close event on close now (ee0db01)
• connect: prevent multiple callbacks in error scenarios (5f6a787)
• monitoring: incorrect states used to determine rescheduling (ec1e04c)
• pool: don't reset a pool if we'not already connected (32316e4)
• pool: only transition to DISCONNECTED if reconnect enabled (43d461e)
• replset: don't leak servers failing to connect (f209160)
• replset: use correct topologyId for event emission (19549ff)
• sdam: minHeartbeatIntervalMS => minHeartbeatFrequencyMS (af9fb45)
• sdam: don't emit close every time a child server closes (818055a)
• sdam: don't lose servers when they fail monitoring (8a534bb)
• sdam: don't remove unknown servers in topology updates (1147ebf)
• sdam: ignore server errors when closing/closed (49d7235)
• server: don't emit error in connect if closing/closed (62ada2a)
• server: ensure state is transitioned to closed on connect fail (a471707)
• topology: report unified topology as nodejs (d126665)
• topology: set max listeners to infinity for db event relay (edb1335)

Features

• sdam_viz: add new tool for visualizing driver sdam changes (738189a)
• sdam_viz: support legacy topologies in sdam_viz tool (1a5537e)
• update-hints: add support for hint to all update methods (720f5e5)

v3.3.3

Compare Source

Bug Fixes

• change_stream: emit 'close' event if reconnecting failed (f24c084)
• ChangeStream: remove startAtOperationTime once we have resumeToken (362afd8)
• connect: Switch new Buffer(size) -> Buffer.alloc(size) (da90c3a)
• MongoClient: only check own properties for valid options (9cde4b9)
• mongos: disconnect proxies which are not mongos instances (ee53983)
• mongos: force close servers during reconnect flow (186263f)
• monitoring: correct spelling mistake for heartbeat event (21aa117)
• replset: correct server leak on initial connect (da39d1e)
• replset: destroy primary before removing from replsetstate (45ac09a)
• replset: destroy servers that are removed during SDAM flow (9ea0190)
• saslprep: add in missing saslprep dependency (41f1165)
• topology: don't early abort server selection on network errors (2b6a359)
• topology: don't emit server closed event on network error (194dcf0)
• topology: include all BSON types in ctor for bson-ext support (aa4c832)
• topology: respect the force parameter for topology close (d6e8936)

Features

• Update: add the ability to specify a pipeline to an update command (#​2017) (44a4110)
• urlParser: default useNewUrlParser to true (52d76e3)

v3.3.2

Compare Source

Bug Fixes

• change-stream: default to server default batch size (b3ae4c5)
• execute-operation: return promise on session support check (a976c14)
• gridfs-stream: ensure close is emitted after last chunk (ae94cb9)

v3.3.1

Compare Source

Bug Fixes

• find: respect client-level provided read preference (fec4f15)
• correct inverted defaults for unified topology (cf598e1)

v3.3.0

Compare Source

Bug Fixes

• aggregate-operation: move type assertions to constructor (25b27ff)
• autoEncryption: tear down mongocryptd client when main client closes (fe2f57e)
• autoEncryption: use new url parser for autoEncryption client (d3670c2)
• Bulk: change BulkWriteError message to first item from writeErrors (#​2013) (6bcf1e4)
• change_stream: emit 'close' event if reconnecting failed (41aba90)
• change_stream: emit close event after cursor is closed during error (c2d80b2)
• change-streams: don't copy irrelevant resume options (f190072)
• changestream: removes all event listeners on close (30eeeb5)
• ChangeStream: remove startAtOperationTime once we have resumeToken (8d27e6e)
• ClientSessions: initialize clientOptions and cluster time (b95d64e)
• connect: don't treat 'connect' as an error event (170a011)
• connect: fixed syntax issue in connect error handler (ff7166d)
• connections_stepdown_tests: use correct version of mongo for tests (ce2c9af)
• createCollection: Db.createCollection should pass readConcern to new collection (#​2026) (6145d4b)
• cursor: do not truncate an existing Long (317055b), closes mongodb-js/mongodb-core#​441
• distinct: return full response if full option was specified (95a7d05)
• MongoClient: allow Object.prototype items as db names (dc6fc37)
• MongoClient: only check own properties for valid options (c9dc717)
• OpMsg: cap requestIds at 0x7fffffff (c0e87d5)
• read-operations: send sessions on all read operations (4d45c8a)
• ReadPreference: improve ReadPreference error message and remove irrelevant sharding test (dd34ce4)
• ReadPreference: only allow valid ReadPreference modes (06bbef2)
• replset: correct legacy max staleness calculation (2eab8aa)
• replset: introduce a fixed-time server selection loop (cf53299)
• server: emit "first connect" error if initial connect fails due to ECONNREFUSED (#​2016) (5a7b15b)
• serverSelection: make sure to pass session to serverSelection (eb5cc6b)
• sessions: ensure an error is thrown when attempting sharded transactions (3a1fdc1)
• topology: add new error for retryWrites on MMAPv1 (392f5a6)
• don't check non-unified topologies for session support check (2bccd3f)
• maintain internal database name on collection rename (884d46f)
• only check for transaction state if session exists (360975a)
• preserve aggregate explain support for legacy servers (032b204)
• read concern only supported for mapReduce without inline (51a36f3)
• reintroduce support for 2.6 listIndexes (c3bfc05)
• return executeOperation for explain, if promise is desired (b4a7ad7)
• validate atomic operations in all update methods (88bb77e)
• transactions: fix error message for attempting sharded (eb5dfc9)
• transactions: fix sharded transaction error logic (083e18a)

Features

• Aggregate: support ReadConcern in aggregates with $out ([21cdcf0](https://togithub.com/

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by WhiteSource Renovate. View repository job log here.