search

mulesoft-labs / osprey-resources

Automatically support RAML resources
Other
2 stars 7 forks source link

An in-range update of osprey-router is breaking the build 🚨 #10

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency osprey-router was updated from 0.6.0 to 0.6.1.

🚨 View failing branch.

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

osprey-router 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-labs/osprey-resources/builds/465163098?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 8 commits.

  • 134bc4e 0.6.1
  • 15cb405 package lock
  • 1796b0e Sync package-lock
  • 2ed4444 Merge remote-tracking branch 'origin/greenkeeper/popsicle-10.0.0' into develop
  • 063157d Merge remote-tracking branch 'origin/greenkeeper/standard-12.0.0' into develop
  • 72fd8aa Update node version in travis
  • cb1d371 chore(package): update standard to version 12.0.0
  • ab34dde 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 0.6.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.