Skip to content

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

@greenkeeper

Description

@greenkeeper

Version 2.6.4 of debug just got published.

Branch Build failing 🚨
Dependency debug
Current Version 2.6.3
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
  • continuous-integration/travis-ci/push The Travis CI build failed Details

  • coverage/coveralls First build on greenkeeper/debug-2.6.4 at 94.298% Details

Commits

The new version differs by 6 commits .

  • f311b10 release 2.6.4
  • 1f01b70 Fix bug that would occure if process.env.DEBUG is a non-string value. (#444)
  • 2f3ebf4 Update CHANGELOG.md
  • f5ae332 Update CHANGELOG.md
  • 9742c5f chore(): ignore bower.json in npm installations. (#437)
  • 27d93a3 update "debug" to v0.7.3

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 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions