An in-range update of @types/node is breaking the build 🚨
Closed this issue · 6 comments
The devDependency @types/node was updated from 10.10.0 to 10.10.1.
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
- ✅ ci/circleci: node-latest: Your tests passed on CircleCI! (Details).
- ✅ ci/circleci: node-8: Your tests passed on CircleCI! (Details).
- ✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
- ✅ codecov/project: No report found to compare against (Details).
- ✅ codecov/patch: Coverage not affected. (Details).
- ❌ Build: We could not find a valid build file. Please ensure that your repo contains a cloudbuild or a Dockerfile.
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 10.10.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency@types/node was updated from10.10.1to10.10.2.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
- The
devDependency@types/node was updated from10.10.2to10.10.3.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
- The
devDependency@types/node was updated from10.10.3to10.11.0.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
- The
devDependency@types/node was updated from10.11.0to10.11.1.
Your tests are still failing with this version. Compare changes
- The
devDependency@types/node was updated from10.11.1to10.11.2.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀