search

mulesoft-labs / osprey-mock-service

Generate an API mock service from a RAML definition using Osprey
Other
111 stars 35 forks source link

An in-range update of osprey-resources is breaking the build 🚨 #59

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency osprey-resources was updated from 0.8.0 to 0.8.1.

🚨 View failing branch.

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

osprey-resources 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-mock-service/builds/465163884?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 8 commits.

  • 2f2d8dc 0.8.1
  • afe319d package lock
  • 785ecaf Sync package-lock
  • d027204 Merge remote-tracking branch 'origin/greenkeeper/standard-12.0.0' into develop
  • 8b82e68 Merge remote-tracking branch 'origin/greenkeeper/popsicle-10.0.0' into develop
  • 69e197b Update travis node versions
  • 7f49563 chore(package): update standard to version 12.0.0
  • 83d7b3f 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.8.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.