An in-range update of npm-check-updates is breaking the build 🚨

[greenkeeper[bot]]

The devDependency npm-check-updates was updated from 3.1.16 to 3.1.17.

🚨 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/555845909?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 3 commits.

• 7dad06a 3.1.17
• 53ccf06 Merge pull request #561 from stoically/basic-legacy-auth-token
• bc13c72 Support npm registry basic legacy auth

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:

[greenkeeper[bot]]

After pinning to 3.1.16 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

• The devDependency npm-check-updates was updated from 3.1.17 to 3.1.18.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• cd7e9c5 3.1.18
• c5bd0a8 Merge pull request #563 from stoically/authinfo-cleanup
• 4a32785 Cleanup npm auth info (#556)

See the full diff