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

[greenkeeper]

Version 2.6.2 of rimraf just got published.

Branch	Build failing 🚨
Dependency	rimraf
Current Version	2.6.1
Type	devDependency

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

As rimraf is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 2 commits.

• 79b933f v2.6.2
• 38b907f Fix #159, correct 0o666 chmod

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 2.6.1 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.2 to 2.6.3.

Your tests are still failing with this version. Compare changes

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