An in-range update of npm-run-all is breaking the build 🚨

[greenkeeper]

The devDependency npm-run-all was updated from 4.1.3 to 4.1.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

npm-run-all 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 failed (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

---

Commits

The new version differs by 3 commits.

• a79fbac 🔖 4.1.4
• d97929c remove test in version script temporary
• 57d72eb 🔥 remove ps-tree

See the full diff

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 🌴

[greenkeeper]

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

[greenkeeper]

• The devDependency npm-run-all was updated from 4.1.4 to 4.1.5.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

• df15118 🔖 4.1.5
• 94007fd ⚒ make test's timeout longer
• 1b41ac5 🐛 use pidtree
• 7ec542e ⬆️ update dependencies
• 51e678e Revert: "remove test in version script temporary"

See the full diff