Update hapi to version 16.0.0 🚀 #43
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 ✨
You rock!
🌴
The new version differs by 231 commits .
3c1d6beCall dep. For #3396386bb94Closes #3381b617d63Closes #33476735fdbTest for #337068d6ea7Cleanup for #324210bcdaaMerge pull request #3358 from turtleDev/master9676577Cleanup for #33725c10b22Merge pull request #3372 from dahjelle/fix-graceful-restarts-for-longpoll-and-https09c2e33Prevent error headers from being modified. Closes #33784596dd9Merge pull request #3380 from wwalser/reusable-boomsdb8ffbfMerge branch 'master' of github.com:hapijs/hapi0ca8ceaUpdate 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 #3397f9c51efRegression test to ensure that Error objects can also be reused the same as Boom objects.5322910Response to code review, clone boom.output instead of just boom.output.headers.b700774Proposed fix for issue #3378.There are 231 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade