This version is covered by your current version range and after updating it in your project the build went from success to failure.
As mongoose is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Coverage remained the same at 100.0% when pulling 80cc64d74d72a134b47b0fe0d39d55b23e3f7108 on greenkeeper-mongoose-4.5.4 into fcb0dbbe857e91c7f172eaef8447fab9cf13f9b5 on master.
Coverage remained the same at 100.0% when pulling 5f47b3f9d8844386c85b9da04f93bd49e0520bb3 on greenkeeper-mongoose-4.5.4 into 4d8d04c547a638dd63f564d6ae67bbfcdebb2b2d on master.
Coverage remained the same at 100.0% when pulling 75c80541cf5b22159c2209fbea1f6242c6584ba5 on greenkeeper-mongoose-4.5.4 into 0320c89039257ae7885ab05687f63654feffa255 on master.
Coverage remained the same at 100.0% when pulling 7a8b44fe7c8d87a48abe968ed7a0f110fa4c1819 on greenkeeper-mongoose-4.5.4 into 0f6cdaec571494e63aad88d9d6ba22d0c58299fb on master.
Hello lovely humans,
mongoose just published its new version 4.5.4.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As mongoose is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 221 commits .
7398862
chore: release 4.5.4
3cf2ad9
Merge branch 'master' of github.com:Automattic/mongoose
5e385ae
fix(aggregate): allow passing obj to .unwind()
592056d
test(aggregate): repro #4239
a900a30
Merge pull request #4302 from simonxca/doc-fixes
ad3930d
Merge pull request #4309 from RoCat/master
d330135
fix(document): allow setting empty obj if strict mode is false
9262402
test(document): repro #4274
76ea425
fix(populate): handle deeply nested virtual populate
a61071e
test(populate): repro #4278
462a80d
doc(schema) changed schema.static() params to match schema.method()
ccab73e
fix(populate): convert single result to array for virtual populate because of lean
b1d8303
test(populate): repro #4288
0f5d0a0
Merge branch 'master' of github.com:Automattic/mongoose
1eeddb5
fix(populate): handle empty results for populate virtuals properly
There are 221 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade