An in-range update of debug is breaking the build π¨
greenkeeper opened this issue Β· comments
Version 2.4.0 of debug just got published.
Branch | Build failing π¨ |
---|---|
Dependency | debug |
Current Version | 2.3.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
Commits
The new version differs by 7 commits .
b82d4e6
release 2.4.0
41002f1
Update bower.json (#342)
e58d54b
Node: configurable
util.inspect()
options (#327)00f3046
Node:
%O
(big O) pretty-prints the object (#322)bd9faa1
allow colours in workers (#335)
501521f
Use same color for same namespace. (#338)
e2a1955
Revert "handle regex special characters"
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 π΄
After pinning to 2.3.3 your tests are passing again. Downgrade this dependency π.
Version 2.4.1 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
Version 2.4.3 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
Commits
The new version differs by 8 commits .
e1ee4d5
release 2.4.3
e4b8bb9
Fix #363 (#364)
4c3e80d
release 2.4.2
5783966
fix browser colors (#367)
a5bbe13
travis ci integration
f77ca5d
added linting and testing boilerplate with sanity check
803fb05
release 2.4.1
94d78b5
Fixed a typo (#356)
See the full diff.