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

[greenkeeper[bot]]

Version 5.4.0 of semver just got published.

Branch	Build failing 🚨
Dependency	semver
Current Version	5.3.0
Type	devDependency

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

As semver is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details

- ✅ **percy/package-hint-historic-resolver** Visual review automatically approved. No visual diffs found. [Details](https://percy.io/kellyselden/package-hint-historic-resolver/builds/294683) - ✅ **coverage/coveralls** First build on greenkeeper/semver-5.4.0 at 90.882% [Details](https://coveralls.io/builds/12525272) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/kellyselden/package-hint-historic-resolver/builds/256964064?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 16 commits.

• e1c49c8 v5.4.0
• 3ebc11d more test coverage
• 5b30513 speed up tests a lot, add coverage
• e1668ce add top level intersects function
• 6cb2bcb intersection: use semver.version, not semver.raw
• 4bacbfa Make exposed apis more clear
• 8b86a26 Reduce line length and remove unused platform parameter
• 99f133e Add range and comparator intersection docs to README
• afbe8ca Move methods to comparator and range
• 67c9ed7 Add support for range and comparators comparison
• caeeac4 remove 0.x from Travis, cache npm stuff, use containers
• bdda1a4 Add Node.js 8 to .travis.yml
• 8fff305 Add node 6 to travis
• aaba710 Added syntax highlighting to readme example
• 32802c5 minimize heap allocations for maxSatisfying/minSatisfying

There are 16 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 5.3.0 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper[bot]]

Version 5.4.1 just got published.

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

Commits

The new version differs by 2 commits.

• 0877c94 v5.4.1
• 7be83d1 Handle bad ranges in max/min satisfying

See the full diff