Open greenkeeper[bot] opened 6 years ago
After pinning to 10.5.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes π¨
Your tests are passing again with this version. Explicitly upgrade to this version π
Your tests are passing again with this version. Explicitly upgrade to this version π
Your tests are passing again with this version. Explicitly upgrade to this version π
Your tests are still failing with this version. Compare the changes π¨
Your tests are passing again with this version. Explicitly upgrade to this version π
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are passing again with this version. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.9.4
to 10.10.0
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.10.0
to 10.10.1
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.10.1
to 10.10.2
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.10.2
to 10.10.3
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.10.3
to 10.11.0
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.11.0
to 10.11.1
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.11.1
to 10.11.2
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.11.2
to 10.11.3
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.11.3
to 10.11.4
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.11.4
to 10.11.5
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.11.5
to 10.11.6
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.11.6
to 10.11.7
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.11.7
to 10.12.0
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.0
to 10.12.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.1
to 10.12.2
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.2
to 10.12.3
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.3
to 10.12.4
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.4
to 10.12.5
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.5
to 10.12.6
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.6
to 10.12.7
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.7
to 10.12.8
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.8
to 10.12.9
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.9
to 10.12.10
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.10
to 10.12.11
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.11
to 10.12.12
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.12
to 10.12.13
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.13
to 10.12.14
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.14
to 10.12.15
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.16
to 10.12.17
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.16
to 10.12.17
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.17
to 10.12.18
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.21
to 10.12.22
.Your tests are still failing with this version. Compare changes
devDependency
@types/node was updated from 10.12.22
to 10.12.23
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@types/node was updated from 10.12.23
to 10.12.24
.Your tests are still failing with this version. Compare changes
Version 10.5.2 of @types/node was just published.
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
- β **continuous-integration/appveyor/branch** AppVeyor build succeeded [Details](https://ci.appveyor.com/project/Narazaka/narloader/build/154) - β **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/Ikagaka/NarLoader/builds/400680183?utm_source=github_status&utm_medium=notification)FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: