mulesoft / osprey

Generate Node.JS API middleware from a RAML definition
Other
431 stars 66 forks source link

An in-range update of request-error-handler is breaking the build 🚨 #177

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency request-error-handler was updated from 1.1.0 to 1.1.1.

🚨 View failing branch.

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

request-error-handler is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/mulesoft/osprey/builds/465161137?utm_source=github_status&utm_medium=notification)).

Commits

The new version differs by 15 commits.

  • cdd2270 1.1.1
  • 32ddbbc package lock
  • 645eab8 Merge pull request #9 from mulesoft-labs/greenkeeper/debug-4.0.0
  • eb46813 Merge fresh develop
  • 4b82186 Merge pull request #10 from mulesoft-labs/greenkeeper/standard-12.0.1
  • 730994c Merge dev
  • 3fa2402 Merge branch 'develop' into greenkeeper/standard-12.0.1
  • 08ae44e Merge pull request #6 from mulesoft-labs/greenkeeper/popsicle-10.0.0
  • 7cd66fa Update popsicle-server. Fix deprecated popsicle api
  • 58f84e3 Merge branch 'develop' into greenkeeper/popsicle-10.0.0
  • 1e25e8f Update travis nodejs
  • 40b5486 chore(package): update lockfile
  • fd81085 fix(package): update debug to version 4.0.0
  • daebd54 chore(package): update standard to version 12.0.1
  • 8384e1a chore(package): update popsicle to version 10.0.0

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

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