Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of hapi is breaking the build 🚨 #107

Closed
greenkeeper bot opened this issue Sep 24, 2017 · 1 comment
Closed

An in-range update of hapi is breaking the build 🚨 #107

greenkeeper bot opened this issue Sep 24, 2017 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Sep 24, 2017

Version 16.6.1 of hapi just got published.

Branch Build failing 🚨
Dependency hapi
Current Version 16.6.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As hapi is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 7 commits.

  • d1cb638 Upgrade joi. Closes #3585
  • 5af4d2c Merge pull request #3582 from hapijs/joi11-paths
  • edf18b2 Support joi 11 paths arrays. Fixes #3581.
  • e4b2780 Merge branch 'master' of github.com:hapijs/hapi
  • bc1a2dc Break some big functions
  • f7dd308 Update SPONSORS.md
  • 9e3d5b9 Update version

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 24, 2017

After pinning to 16.6.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant