An in-range update of @types/node is breaking the build π¨
Closed this issue Β· 6 comments
The devDependency @types/node was updated from 13.5.2
to 13.5.3
.
π¨ 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
- β ROS Eloquent Elusor: null
- β ROS Dashing Diademata: null
- β ROS Melodic Morenia: null
- β ROS and ROS 2 Binary Install Test Suite (Linux only): null
- β test (windows-latest): null
- β test (ubuntu-18.04): null
- β test (macOS-latest): There are 1 failures, 0 warnings, and 0 notices.
- β ROS Kinetic Kame: null
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 13.5.2 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 from13.5.3
to13.7.0
.
Your tests are passing again with this update. Explicitly upgrade to this version π
- The
devDependency
@types/node was updated from13.7.0
to13.7.1
.
Your tests are passing again with this update. Explicitly upgrade to this version π
- The
devDependency
@types/node was updated from13.7.1
to13.7.2
.
Your tests are still failing with this version. Compare changes
- The
devDependency
@types/node was updated from13.7.2
to13.7.3
.
Your tests are passing again with this update. Explicitly upgrade to this version π
- The
devDependency
@types/node was updated from13.7.3
to13.7.4
.
Your tests are still failing with this version. Compare changes