Hello lovely humans,

rimraf just published its new version 2.6.1.

This version is covered by your current version range and after updating it in your project the build went from success to failure.

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 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

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 16 commits .

• d84fe2c v2.6.1
• e8cd685 only run rmdirSync 'retries' times when it throws
• 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

There are 16 commits in total. See the full diff.