An in-range update of mongoose is breaking the build 🚨

[greenkeeper[bot]]

The dependency mongoose was updated from 5.2.16 to 5.2.17.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/NFive/hub/builds/431668344?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 13 commits.

• ee17056 chore: release 5.2.17
• a9db83e docs(model+query): explain which operators count() supports that countDocumnts() doesn't
• 53f7a24 docs(guide): clarify that Mongoose only increments versionKey on save() and add a workaround for findOneAndUpdate()
• c1bdbcf fix(update): find top-level version key even if there are $ operators in the update
• abe4545 test(model): repro #7003
• f3bda5e Merge pull request #7024 from lineus/feat-query.setUpdate
• 8be1dbf Merge branch 'master' into feat-query.setUpdate
• f88cfdf Merge pull request #7034 from lineus/docs-7018
• ff0f2dc Merge pull request #7036 from lineus/fix-6922
• 0e9d6d3 fix typo in model.js
• e7f9ed0 add debug output stream change to migration doc
• b30edd1 chore: now working on 5.2.17
• 89b57c5 add setUpdate to Query.prototype

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:

[greenkeeper[bot]]

After pinning to 5.2.16 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.