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

[greenkeeper]

The dependency semver was updated from 6.1.2 to 6.1.3.

🚨 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 passed (Details).
• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 3 commits.

• 3dc88f3 6.1.3
• c44e124 Handle X ranges properly in includePrelease mode
• ba19e8f Add a -0 prerelease on >X and <X ranges

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.1.2 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

• The dependency semver was updated from 6.2.0 to 6.3.0.

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

Commits

The new version differs by 7 commits.

• 0eeceec 6.3.0
• 2779d96 Expose the token enum on the exports
• 9f5f615 changelog
• ce6190e 6.2.0
• 24af461 Add test coverage for bin file
• 388ec1c Add rtl option to coerce from right to left
• d062593 coerce(number) will coerce to a string

See the full diff