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 is breaking the build 🚨 #60

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency osprey was updated from 0.5.0 to 0.5.1.

🚨 View failing branch.

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

osprey 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/465166732?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 21 commits.

  • 982aa9e 0.5.1
  • b27fe42 package lock
  • 5050544 Merge pull request #163 from mulesoft/greenkeeper/popsicle-10.0.0
  • db90b32 Fix popsicle 10 merge API issues
  • 5ebed70 Merge branch 'develop' into greenkeeper/popsicle-10.0.0
  • aae37c9 Fix lint errors
  • fb279ae Fix conflict after debug 4 update
  • 906f34e Merge remote-tracking branch 'origin/greenkeeper/standard-12.0.0' into develop
  • 607e342 Sync package-lock
  • ba08583 Fix conflict
  • 61c5b3e Merge remote-tracking branch 'origin/greenkeeper/rewire-4.0.0' into develop
  • be6c552 Update node version in travis file
  • b614444 Merge pull request #172 from mulesoft/update_dependencies
  • dbbcf5f adds @jstoiko requested changes
  • db9e086 updates libs

There are 21 commits in total.

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.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.