-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of debug is breaking the build 🚨 #7
Comments
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 🚀 CommitsThe new version differs by 8 commits .
See the full diff. |
Version 2.4.4 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 10 commits .
See the full diff. |
Version 2.4.5 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 16 commits .
There are 16 commits in total. See the full diff. |
Version 2.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 42 commits .
There are 42 commits in total. See the full diff. |
Version 2.5.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 2.5.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 10 commits .
See the full diff. |
Version 2.6.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 14 commits .
See the full diff. |
Version 2.6.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.6.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits .
See the full diff. |
Version 2.6.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.6.4 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 6 commits .
See the full diff. |
Version 2.6.6 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 2.6.7 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 14 commits.
See the full diff |
Version 2.6.8 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 2.4.0 of debug just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As debug 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
✅ bitHound - Dependencies No failing dependencies. Details
✅ bitHound - Code No failing files. 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 🌴
The text was updated successfully, but these errors were encountered: