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

[greenkeeper]

Version 11.1.1 of should just got published.

Branch	Build failing 🚨
Dependency	should
Current Version	11.1.0
Type	devDependency

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

As should 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

• ✅ dependency-ci Dependencies checked Details

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

Commits

The new version differs by 7 commits .

• 63c9b56 Release 11.1.1
• 5487a80 Update Readme.md
• 28160d5 Merge branch 'master' of github.com:shouldjs/should.js
• ba0093e Update Readme.md
• c60e331 Update Readme.md
• 12d9ec7 Merge pull request #120 from Awk34/patch-1
• b2df8b8 docs(history): fix 11.0.0 language/etc

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