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

[greenkeeper]

Version 2.6.0 of rimraf just got published.

Branch	Build failing 🚨
Dependency	rimraf
Current Version	2.5.4
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 could not complete due to an error Details

Commits

The new version differs by 5 commits .

• 5b661e4 v2.6.0
• c09915f update tap
• d53235d Make rimraf.sync 10000% more reliable on Windows
• e8b10a7 Retry on EBUSY et al on non-windows platforms as well
• 0fac5f7 Add --no-glob option to cli

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]

Version 2.6.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits .

• d84fe2c v2.6.1
• e8cd685 only run rmdirSync 'retries' times when it throws

See the full diff.