This version 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 unexpected-http.
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.
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 800ba67b3bc36891a0d232d66e1ad37b383d49b5 on greenkeeper-unexpected-http-6.0.0 into eaa621215e2267d625dbcc43d5b810085ea6a282 on master.
Hello lovely humans,
unexpected-http just published its new version 6.0.0.
This version 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 unexpected-http. 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.
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 11 commits .
4063b83
6.0.0
d710340
Merge branch 'feature/child'
a9ee941
Update unexpected-messy to 7.0.0, drop it and messy as peer deps, update Unpexected to 10.27.0.
c0e8f10
Documentation: Fix typos
976d613
Documentation: Fix quoting of tag soup-like syntax
26d0f54
Tests: Adjust timeouts to avoid bogus CI failures.
95cfb6d
Travis: Test with node.js 7
d65ac08
Revert me: Update unexpectedjs/unexpected#d10718ac1a1e3dc90f3dadacafd391132e4ebc94
1818a01
Revert me: Update to unexpectedjs/unexpected-messy#ee9720dd98d30ca59f72ec93cd25bb5355ec654f
51cd5a2
Revert me: Switch to unexpectedjs/unexpected#7077341f4ecc25e56f55928eed91cabfb438418c (tip of feature/child).
bd6b874
Install unexpected-messy in a child and export the main assertion
See the full diff.
Screencast
Try it today. Free for private repositories during beta.