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

[greenkeeper]

The dependency osprey was updated from 0.5.1 to 0.5.2.

🚨 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).

---

Commits

The new version differs by 7 commits.

• 0c29d59 0.5.2
• 7cdd55d bump dependencies
• 6eff3fd Migrate from istanbul to nyc
• ed5a7bc Merge pull request #183 from mulesoft/greenkeeper/initial
• 4e8c1a1 Downgrade osprey
• cfa3040 chore(package): update lockfile package-lock.json
• 8f31b7d chore(package): update dependencies

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[greenkeeper]

• The dependency osprey was updated from 0.5.2 to 0.5.3.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀