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

[greenkeeper[bot]]

Version 10.7.0 of tap just got published.

Branch	Build failing 🚨
Dependency	tap
Current Version	10.6.0
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

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/fnogatz/xsd2json/builds/246718826?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 10 commits.

• c417424 v10.7.0
• 802cf70 update 'only' output test
• dc67c58 add t.only()
• 0f474d9 filter out --only and --grep skip messages
• efd024d consolidate --only tests
• f60b060 Further refining --only
• 0d0ac05 runner test for --only
• 7550694 update usage, add -O alias for --only
• 8438249 add test for --only flag
• 7e42a08 WIP TAP_ONLY, --only, {only: true} and warning to stderr if {only: true} but tap’s only option is not true

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:

[greenkeeper[bot]]

After pinning to 10.6.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[fnogatz]

Solved via 89c14c5 in #72.