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

[greenkeeper]

Version 1.5.2 of assume just got published.

Branch	Build failing 🚨
Dependency	assume
Current Version	1.5.1
Type	devDependency

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

As assume 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 2 commits.

• 1ba22b6 [dist] 1.5.2
• bf9afff [fix] Include actual length in .length/.size assertion message (#22)

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 🌴

[greenkeeper]

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