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

## Version **10.6.0** of [tap](https://github.com/tapjs/node-tap) just got published.

Branch


Build failing 🚨




Dependency


tap




Current Version


10.5.2




Type


devDependency

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

As tap 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

- ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/documentationjs/documentation-theme-utils/22?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)

---

Commits

The new version differs by 7 commits.

• 090a8ee v10.6.0


• f60b003 fix rcfile test for grep and grepInvert fields


• 0e36c2a doc TAP_GREP and TAP_GREP_INVERT environs in cli usage


• 780f14a inherit grepInvert as well as greps


• b4a6c8f update tests for grepInvert fix


• 3c62917 grepInvert defaults to false, not []


• 7e94cfc add --grep option

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](https://greenkeeper.io) Bot :palm_tree:

Start by checking the tap devDependency declaration and the failed ci/circleci run linked in the issue. Compare tap 10.5.2 with 10.6.0 and identify the build failure; done means the dependency update is compatible and the CircleCI tests pass.

Written by the indexing model from the issue text.