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

[greenkeeper]

The dependency semver was updated from 6.0.0 to 6.1.0.

🚨 View failing branch.

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

semver 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.

• 0aea9ca 6.1.0
• 7b072bd Range intersect supports wildcards and ~
• 78ea02a tap@14
• 62b21ed Remove --save option as it isn't required anymore
• 93c2f2d Clarify some ^0.0.x & ~.0.0.x cases
• e09ecf8 Clarify Caret Ranges
• a3bcc39 Add semver.compareBuild function.

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