-
-
Notifications
You must be signed in to change notification settings - Fork 5
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 🚨 #21
Comments
After pinning to 11.13.4 your tests are passing again. Downgrade this dependency 📌. |
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 still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare 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 still failing with this version. Compare 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 still failing with this version. Compare 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 still failing with this version. Compare 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 still failing with this version. Compare 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 🚀 |
The devDependency @types/node was updated from
11.13.4
to11.13.5
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: