mocha@2.4.1 breaks build 🚨

[greenkeeperio-bot]

Hello :wave:

:rotating_light::rotating_light::rotating_light:

mocha just published its new version 2.4.1, which is covered by your current version range. After updating it in your project the build went from success to failure.

This means your software is now malfunctioning, because of this update. Use this branch to work on adaptions and fixes.

Happy fixing and merging :palm_tree:

---

The new version differs by 69 commits .

• aa550e1 Release v2.4.1
• 33b7261 rebuild mocha.js
• 761fa17 rename HISTORY.md => CHANGELOG.md
• 623c9b6 increase retry test timeout
• f00c197 Merge pull request #2068 from danielstjules/dstjules/test-body
• d59cc6c Fix #2067: HTML/DOC reporter regression with async failures
• a25ac95 Build browser mocha for 2.4.0
• aa25b1c Release 2.4.0
• 9f6cb87 Merge pull request #2066 from danielstjules/dstjules/fix-browser
• 02062fa Fix test fn's being deleted too early for browser reporter
• 8522755 Merge pull request #1945 from ryanshawty/master
• c97d03a Correctly skip tests when skipping in a suites before()
• b64d76c Merge pull request #2056 from pra85/patch-1
• fdf01b5 chore(license): update license year to 2016
• 65e2984 Fix integration tests: remove .only()

There are 69 commits in total. See the full diff.

---

This pull request was created by greenkeeper.io. It keeps your software, up to date, all the time.

_{Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster :zap:}

[cben]

Not sure if this random flakiness or related to mocha upgrade.

At first I assumed the commit can have no effect, since I have a npm-shrinkwrap.json (which greenkeeper doesn't understand yet). But all test runs did get the new mocha 2.4.1 installed? Aha! devDependencies are not shrinkwrapped!