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

Nobody has claimed this yet.

## The devDependency [rimraf](https://github.com/isaacs/rimraf) was updated from `2.6.3` to `2.7.0`.

🚨 [View failing branch](https://github.com/linkedin/opticss/compare/master...linkedin:greenkeeper%2Fdefault%2Frimraf-2.7.0).

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

rimraf is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/linkedin/opticss/builds/571588730?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 2 commits.

• 250ee15 2.7.0


• dc1682d feat: make it possible to omit glob dependency

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start with the failing branch and the linked Travis CI build details to identify why the rimraf 2.7.0 update breaks the build. Inspect the dependency manifest and relevant build or test commands, then verify that the build passes with the compatible dependency configuration.

Written by the indexing model from the issue text.