This version is covered by your current version range and after updating it in your project the build went from success to failure.
As unexpected-http 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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 85.083% when pulling ebf94560546853ee13e5a2f40052bba3ce623206 on greenkeeper-unexpected-http-5.7.0 into 03e38ab39909e7e74620eb0f80e03ec4fa7eaabb on master.
Hello lovely humans,
unexpected-http just published its new version 5.7.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As unexpected-http 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 24 commits .
66b5a93
5.7.0
fef3313
Avoid passing the 'timeout' parameter to messy now that 6.16.0 prohibits unsupported properties
2594352
Update messy to ^6.16.0
4fd9020
Promisify properly.
4f837a3
Test that the context is provided as the fulfillment value.
056e4bb
Test: Remove bogus 'next' parameters.
6061150
Use new expect.shift syntax and compound assertions.
6ef4124
Update unexpected to 10.26.3.
fc63d07
Breaking change: Don't treat a response given as a string or buffer as a shorthand for a response with that body
28d222b
Use unexpected-messy's support for satifying an HTTP response against a number
5250333
Update messy to ^6.15.2 and unexpected-messy to ^6.5.0.
4837618
Test that the response can be specified as a number.
c42bcfa
update eslint (2.13.1) and eslint-config-onelint (1.2.0)
93a9080
5.6.0
726f10b
Update browserify & link an http polyfill that allows disabling fetch API use.
There are 24 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.