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

[greenkeeper]

Version 3.5.2 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.5.1
Type	devDependency

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

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

v3.5.2

3.5.2 / 2017-09-10

🐛 Fixes

• #3001: Fix AMD-related failures first appearing in v3.5.1 (@boneskull)

Commits

The new version differs by 5 commits.

• 72622ab Release v3.5.2
• ac4c39f fix version in CHANGELOG.md [ci skip]
• f06d969 update CHANGELOG for 3.5.2 [ci skip]
• 9a3ddeb fix AMD bundle by hacking around check in he module; closes #3000
• 337d317 fix broken links in CHANGELOG.md [ci skip]

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

[greenkeeper]

Version 3.5.3 just got published.

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

Release Notes

v3.5.3

3.5.3 / 2017-09-11

🐛 Fixes

• #3003: Fix invalid entities in xUnit reporter first appearing in v3.5.1 (@jkrems)

Commits

The new version differs by 3 commits.

• e838a77 Release v3.5.3
• 4727367 update changelog for v3.5.3 [ci skip]
• 45c870d Use safer XML escaping

See the full diff