Update mongodb to the latest version 🚀 #6497
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io
The dependency mongodb was updated from
3.5.4
to3.5.5
.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Publisher: mbroadst
License: Apache-2.0
Release Notes for v3.5.5
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 eventsby introducing a
ServerDescription
equality operator. Since equality does not take thelastUpdateTime
andlastWriteDate
fields of an ismaster into account, the driver couldeventually 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 driverthinking 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 introducedmaybePromise
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 custompromise library if one was provided!
Thanks very much to all the community members who contributed to this release!
Release Notes
Bug
Commits
The new version differs by 11 commits.
d7ac176
chore(release): 3.5.5
f69f51c
fix: multiple concurrent attempts to process the queue may fail
cde11ec
fix: pass optional promise lib to maybePromise
0c36a32
NODE-2474: update equal server description (#2260)
6b3b64d
test: ensure mock server is setup before continuing with tests
6238c84
fix: correctly use template string for connection string error message
44097c2
test: use a reduced
minHeartbeatFrequencyMS
for spec test runneref04d00
fix(cursor): hasNext consumes documents on cursor with limit
b72fefe
docs: update community links to use MongoDB Community forums
e7dd608
docs: fix typo and formatting of bulletted lists
3ddaa3e
fix: don't depend on private node api for
Timeout
wrapperSee the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴