greenkeeper[bot]
commented
5 years ago After pinning to 3.1.13 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Closed greenkeeper[bot] closed 5 years ago
greenkeeper[bot]
commented
5 years ago After pinning to 3.1.13 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
greenkeeper[bot]
commented
5 years ago devDependency npm-check-updates was updated from 3.1.14 to 3.1.15.Your tests are still failing with this version. Compare changes
greenkeeper[bot]
commented
5 years ago devDependency npm-check-updates was updated from 3.1.15 to 3.1.16.Your tests are still failing with this version. Compare changes
The devDependency npm-check-updates was updated from
3.1.13to3.1.14.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
npm-check-updates 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/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/Chimeejs/chimee/builds/554742632?utm_source=github_status&utm_medium=notification)).Commits
The new version differs by 6 commits.
b525cab3.1.14689b8dcsnyk patch1651392Merge pull request #557 from stoically/registry-url-and-auth-token1c47ea3Make pacote work with scoped registries and auth tokensf20729aMerge pull request #552 from GongT/patch-10deba00remove no more used dependency "package-json"See the full diff
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: