Skip to content

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

@greenkeeper

Description

@greenkeeper

Version 16.6.0 of hapi just got published.

Branch Build failing 🚨
Dependency hapi
Current Version 16.5.2
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/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 21 commits.

  • e4f7bdc Upgrade content. Closes #3570
  • 9c4b2e1 Fix test lint
  • 47a5969 Merge pull request #3563 from fs-opensource/master
  • cb20d4c add header validation step to request lifecycle
  • 5b8c5ff Minor cleanup
  • 2903c44 Minor refactor
  • 5c9281d Merge pull request #3560 from amincheloh/patch-1
  • dc7b3fa Merge pull request #3518 from AJamesPhillips/docs_sameSite
  • 8d1e4e6 Merge pull request #3506 from g-k/add-escape-json-option
  • c1ee17a Update response.js
  • 7e00a19 Update API.md
  • a0f3d2d Merge branch 'master' into add-escape-json-option
  • c7f93a9 add test custom status message
  • bc9edcf fix response.message(httpMessage)
  • f9256ed Docs only reference spec

There are 21 commits in total.

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 🌴

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions