rimraf@2.6.0 breaks build ⚠️

[greenkeeperio-bot]

Hello lovely humans,

rimraf just published its new version 2.6.0.

State	Failing tests ⚠️
Dependency	rimraf
New version	2.6.0
Type	devDependency

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

It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

The new version differs by 14 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
• 2af08bb v2.5.4
• 5ecd321 Clarify assertions: cb is required, options are not
• eb57e2d test to verify custom fs behavior
• 7263a78 v2.5.3
• 9e2c310 Updated glob, tap to latest version
• bc51669 Added travis ci support for modern node versions
• 39f8d1e Use lstat passed in on options object
• 37b4415 Handle windows EPERM when lstat-ing RO dirs
• ef032b6 update tap

See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage remained the same at 100.0% when pulling 984e295 on greenkeeper-rimraf-2.6.0 into 583a75e on master.