hapi@16.3.0 breaks build 🚨 - #42
Open
greenkeeperio-bot wants to merge 13 commits into
Open
Conversation
Update fakeredis to version 2.0.0 🚀
Update ava to version 0.19.1 🚀
geclos
force-pushed
the
master
branch
5 times, most recently
from
May 21, 2018 20:08
763ce3a to
26e2053
Compare
This file contains hidden or 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
2 participants
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.3.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As hapi is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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 51 commits .
1a41f15Merge pull request #3479 from AJamesPhillips/docs-16.1.13d4f0fcMerge pull request #3461 from hapijs/socket-destroyba95396Merge pull request #3441 from kanongil/revise-normalize279def5Cleanup for #3409241d7b0Merge pull request #3409 from gordysc/masterd2de2e7Merge pull request #3504 from kanongil/fix-flaky-test6469604Fix flaky test from #3472081f365Simplify request host updatec212bc8Merge pull request #3472 from kanongil/close-on-payload4fdec0dUpdate transmit.jsca1b9aaUpdate host info on request.setUrl(). Closes #3430c315706Fix several request.url property issues209775aUpdate payload.js052707cUpdate transmit.jse637840Merge branch 'master' into close-on-payloadThere are 51 commits in total. See the full diff.