The version 4.11.6 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of mongoose.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling 802429d10eb9c385bd1dd89e98531d7ff8d66fcd on greenkeeper/mongoose-4.11.6 into 689c6bd23313f3d73e3bfd59c0e9af7f049a6a2a on master.
Version 4.11.6 of mongoose just got published.
The version 4.11.6 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of mongoose. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 40 commits.
b6340c8
chore: release 4.11.6
93e771c
fix: upgrade mongodb -> 2.2.30
d1f6e27
refactor(model): dont hardcode 1000 re: #5529
90b17ae
Merge pull request #5529 from andresattler/master
31a6390
fix(browserDocument): prevent stack overflow caused by double-wrapping embedded doc save() in jest
729ad62
Update model.js
71639e3
refactor(document): get rid of hacky usage of bind()
d39ba28
fix(document): clear single nested doc when setting to empty object
a364c1f
test(document): repro #5506
12126bf
fix: limiting number of async operations per time in insertMany
9db4fdb
chore: add lock file
a8c7c05
fix(populate): ensure nested virtual populate gets set even if top-level property is null
26bd8cf
test(populate): repro #5431
a7df159
fix(connection): emit reconnected and disconnected events correctly with useMongoClient
33ca169
chore: now working on 4.11.6
There are 40 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: