An in-range update of rimraf is breaking the build 🚨

[greenkeeper]

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

🚨 View failing branch.

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

rimraf 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).
• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 6 commits.

• 9442819 2.6.3
• 42fe369 autopublish scripts
• 21fd3df bin test
• 8f1d3a1 update tap and glob for security stuff
• f0bc3a1 update tap, add package-lock
• 692022b travis node version updates

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 2.6.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency rimraf was updated from 2.6.3 to 2.7.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 250ee15 2.7.0
• dc1682d feat: make it possible to omit glob dependency

See the full diff

[greenkeeper]

• The devDependency rimraf was updated from 2.7.0 to 2.7.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• bb57274 2.7.1
• 012ecbb fix: use var instead of let

See the full diff