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-express.
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 increased (+1.07%) to 91.579% when pulling c82f1f73e3fd19685879fb579e7e8752d00a4d4b on greenkeeper-unexpected-express-9.0.0 into c564d47007993bb165e726310345a86f365479db on master.
Coverage increased (+1.07%) to 91.579% when pulling c82f1f73e3fd19685879fb579e7e8752d00a4d4b on greenkeeper-unexpected-express-9.0.0 into c564d47007993bb165e726310345a86f365479db on master.
Hello lovely humans,
unexpected-express just published its new version 9.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-express. 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 32 commits .
37d082a
9.0.0
835f0cb
Merge branch 'feature/child'
2ddb330
Update unexpected to 10.27.0, update unexpected-messy to 7.0.0 and drop it as a peer dep.
c12f05b
Update magicpen-prism to 2.3.0.
b27a21e
Revert me: Update to unexpectedjs/unexpected-messy#ee9720dd98d30ca59f72ec93cd25bb5355ec654f
1c1c3b1
Use expect.child and expect.exportAssertion.
6c6debc
Revert me: Update to unexpectedjs/unexpected#d10718ac1a1e3dc90f3dadacafd391132e4ebc94
616de79
Travis: Stop testing with 0.10 and 0.12, but do test with 7.
a2d0b04
8.5.0
2e8cc03
Added missing mock-fs dependency.
3ac1045
Add ability to upload files in formData by supplying a file system readStream
707ae8b
8.4.0
f343b30
Merge pull request #12 from alexjeffburke/master
0bce39f
Remove unsupportedDone argument which fixes Unexpected 10.26 compatibilty.
720054a
Bump magicpen and magicpen-prism dependencies.
There are 32 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.