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 :muscle:
Status Details
- ❌ **dependency-ci** Failed dependency checks [Details](https://dependencyci.com/builds/151695)
Commits
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 2.6.0 of rimraf just got published.
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 :muscle:
Status Details
- ❌ **dependency-ci** Failed dependency checks [Details](https://dependencyci.com/builds/151695)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](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: