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

## Version **4.1.2** of [tap-spec](https://github.com/scottcorgan/tap-spec) was just published.

Branch


Build failing 🚨




Dependency


tap-spec




Current Version


4.1.1




Type


devDependency

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

tap-spec 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 could not complete due to an error [Details](https://travis-ci.org/developit/babel-preset-es2015-minimal/builds/385215572?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 6 commits.

• 0b3f873 Release 4.1.2


• 810d5ae Merge pull request #60 from maxlutay/check-asserts-length


• 484f694 also check for asserts.length


• 90cb1b8 Merge pull request #51 from vassiliy/feat/mocha_pending_appearance


• 9160ea1 Format pending specs the same way as Mocha


• 8ce610d Create LICENSE

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 by comparing the tap-spec 4.1.1 and 4.1.2 updates and opening the linked Travis CI build to identify the failure. The work is done when the project builds successfully with the updated devDependency, or the dependency range is adjusted if the update is incompatible.

Written by the indexing model from the issue text.