-
Notifications
You must be signed in to change notification settings - Fork 0
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 tap is breaking the build 🚨 #27
Comments
Version 10.3.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 10.4.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 10.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 10.5.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 10.5.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 10.6.0 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 10.7.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 10 commits.
See the full diff |
Version 10.7.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 10.7.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 10.7.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 10.3.3 of tap just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As tap 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
Commits
The new version differs by 6 commits.
ec47ea5
v10.3.3
12255f8
update nyc to 11.0.2 release candidate
7a66dba
--debug removed in node 8
69d6097
bump nyc dep
e0b319a
Drop 0.10 from travis-ci
81aa913
Fix tests on 0.10
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: