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

[greenkeeper]

Version 4.1.2 of chai just got published.

Branch	Build failing 🚨
Dependency	chai
Current Version	4.1.1
Type	devDependency

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

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

---

Release Notes

4.1.2 / 2017-08-31

This release fixes a bug when running in certain environments, and includes a few minor documentation fixes.

Bug Fixes

• fix: update deep-eql to version 3.0.0 (#1020)
• fix: replace code causing breakage under strict CSP (#1032; @Alhadis)

Docs

• docs: add missing assert parameters (#1017, #1023; @Hpauric)
• docs: update year in license file (#1025; @yanca018)

Commits

The new version differs by 8 commits.

• 529d395 Merge pull request #1037 from Cutlery-Drawer/master
• b534fca [email protected]
• c592551 Merge pull request #1032 from Cutlery-Drawer/csp-fix
• 31c3559 Use a hardcoded no-op instead of instancing
• 1ae9386 Merge pull request #1025 from yanca018/master
• 786043b Update license
• 7c1ca16 docs: add missing assert parameters (#1023)
• 6e72c5a fix(package): update deep-eql to version 3.0.0 (#1020)

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