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 hapi.
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.
Coverage remained the same at 100.0% when pulling aff237eca4aeed281dee88a6b94d0a736f8766b5 on greenkeeper-hapi-16.0.0 into c7133e884442a11ff12d2b2518cef42ef8f28d7d on master.
Hello lovely humans,
hapi just published its new version 16.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 hapi. 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 40 commits .
3c1d6be
Call dep. For #3396
386bb94
Closes #3381
b617d63
Closes #3347
6735fdb
Test for #3370
68d6ea7
Cleanup for #3242
10bcdaa
Merge pull request #3358 from turtleDev/master
9676577
Cleanup for #3372
5c10b22
Merge pull request #3372 from dahjelle/fix-graceful-restarts-for-longpoll-and-https
09c2e33
Prevent error headers from being modified. Closes #3378
4596dd9
Merge pull request #3380 from wwalser/reusable-booms
db8ffbf
Merge branch 'master' of github.com:hapijs/hapi
0ca8cea
Update deps. Closes #3383. Closes #3384. Closes #3385. Closes #3386. Closes #3387. Closes #3388. Closes #3389. Closes #3390. Closes #3391. Closes #3392. Closes #3393. Closes #3394. Closes #3395. Closes #3396. Closes #3397
f9c51ef
Regression test to ensure that Error objects can also be reused the same as Boom objects.
5322910
Response to code review, clone boom.output instead of just boom.output.headers.
b700774
Proposed fix for issue #3378.
There are 40 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade