The version 3.1.4 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.
It might be worth looking into these changes and trying to get this project onto the latest version of mongodb.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 726 commits ahead by 726, behind by 49.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 3.1.4 of mongodb was just published.
The version 3.1.4 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.
It might be worth looking into these changes and trying to get this project onto the latest version of mongodb.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 726 commits ahead by 726, behind by 49.
2bbcf53
chore(release): 3.1.4
a029047
feat(core): update mongodb-core to 3.1.3
875b925
chore(pkg): use
standard-version
for release management49406df
chore(pkg): commit yarn and npm lock files
a474158
fix(cursor): remove deprecated notice on forEach
a12aa15
tets(sdam): death to flakey tests!
1eef023
test(replset): reintroduce missing client options
7b6ab57
test(examples): remove duplicated documentation
62336bf
test(find-and-modify): reintroduce missing client options
0bae00f
test(change-streams): const consistency
862fb7c
test(scram-sha-256): correct linting issues recently introduced
c7c10f7
test(sdam): add a wait for sdam events to come in
090404f
test(scram-sha-256): use correct form for passing auth to client
7d4036a
test(sdam): ensure we wait for close to check SDAM events
a184203
test(mongo-client): ensure we are testing the correct client
There are 250 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: