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

[greenkeeper]

Version 2.5.0 of debug just got published.

Branch	Build failing 🚨
Dependency	debug
Current Version	2.4.5
Type	dependency

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

As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very 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 26 commits .

• 355e327 release 2.5.0
• d85c0c6 build perf, fix for bowerfile, fix for webworker
• dc043cf Merge pull request #378 from yamikuronue/replace-babel-with-browserify
• f512cf2 Merge remote-tracking branch 'upstream/master' into replace-babel-with-browserify
• f098331 Merge pull request #388 from ForsakenHarmony/patch-1
• a16cf42 Merge pull request #387 from kribblo/patch-1
• 78e31a8 Update browser.js
• 408ae94 Use typeof window.process !== 'undefined'
• f484cfe fix merge errors
• 23af483 Merge remote-tracking branch 'upstream/master' into replace-babel-with-browserify
• 3e1a15d fix: merged again, because it didn't take. Guess I did it wrong?
• 67182fd fix: Whoops, didn't merge the tests properly. Resolved.
• 2a01c6c Merged from upstream/master. I left the dist/debug in place because my hook now updates it automatically, but I removed the babelrc file since we don't need it anymore.
• 6e934e9 Fix for #381. Moved .babelrc into test folder, where it is used and which is not built with the module. (#383)
• 6a8d525 chore: add coveralls

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

[greenkeeper]

Version 2.5.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 5 commits .

• 3950dae release 2.5.1
• a31178c hotfix for babel-core
• 5a1a36c fix
• b776998 Merge branch 'master' of github.com:visionmedia/debug
• 86d8245 release 2.5.0

See the full diff.

[greenkeeper]

Version 2.5.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 5 commits .

• 9a18d66 release 2.5.2
• eba68ce fix(browser): prevent ReferenceError in workers (#393)
• 280a64d Merge pull request #391 from lurch/patch-1
• 146d0d1 Fix README typo
• ea43614 added notice about v3 api discussion

See the full diff.

[greenkeeper]

Version 2.6.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 4 commits .

• ac5ccae release 2.6.0
• 5895595 better null pointer checks for browser useColors
• 6646130 remove explicit window.debug export (#404)
• 62df220 Deprecate DEBUG_FD (#405)

See the full diff.