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

[Greenkeeper]

Version 4.1.0 of code just got published.

Branch	Build failing 🚨
Dependency	code
Current Version	4.0.0
Type	devDependency

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

As code 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 7 commits.

• 2559673 v4.1.0
• 38df73b print expected value in assertion messages
• df0113b update dependencies and test Node 8
• 461fdb1 add link to Hoek.contain() from includes()
• 3d9dfc3 add NaN() assertion
• d6f7d4b test Node v7 on travis
• c11a9d3 update dependencies

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴