-
Notifications
You must be signed in to change notification settings - Fork 1
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 @types/node is breaking the build 🚨 #50
Comments
Version 7.0.24 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 7.0.25 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 7.0.26 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 7.0.27 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 7.0.28 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 7.0.29 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 7.0.31 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 7.0.32 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.7 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.8 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.9 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.10 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.11 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.12 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.13 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.14 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.15 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.16 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.17 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.19 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.21 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 8.0.22 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Version 7.0.23 of @types/node just got published.
This version is covered by your current version range and after updating it in your project the build failed.
@types/node 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
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: