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 wreck.
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 25 commits .
73e25e8Merge branch 'master' of github.com:hapijs/wreck
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 100.0% when pulling 13dabed2909e614a2915eafc436810776f6f4a0d on greenkeeper-wreck-12.0.0 into bfec24fe5b7deb8fb5a54a2cd688e2c171dc91f2 on master.
Hello lovely humans,
wreck just published its new version 12.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 wreck. 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 25 commits .
73e25e8
Merge branch 'master' of github.com:hapijs/wreck
80bcaf1
version 12.0.0
706ffb7
Fix property reference
fc09382
Document error object in shortcuts
1544728
Merge pull request #164 from kanongil/boom-errors-fix
b661859
Add extra data to boom response errors
34d4ed0
Only create boom errors for shortcut responses
901d521
Merge pull request #163 from geek/master
83e0f2b
Keep request on error status
92e65dc
version 11.0.0
780a83d
Fix redirect test
30b76d2
Merge pull request #161 from geek/master
5cd752e
Fix redirection method for 301, 302
b6906bc
Merge pull request #160 from geek/master
c8a4fe7
Update lab dep
There are 25 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.