An in-range update of @types/node is breaking the build 🚨
greenkeeper opened this issue · 11 comments
Version 8.0.57 of @types/node was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/node |
| Current Version | 8.0.56 |
| Type | devDependency |
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 🌴
After pinning to 8.0.56 your tests are passing again. Downgrade this dependency 📌.
Version 8.0.58 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.0 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.1 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.2 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.3 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.4 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.5 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.6 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.7 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Version 8.5.8 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀