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

[greenkeeper[bot]]

Version 4.9.1 of tape was just published.

Branch	Build failing 🚨
Dependency	tape
Current Version	4.9.0
Type	devDependency

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

tape 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.com/zixia/node-facenet/builds/75703488?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 10 commits.

• 050b318 v4.9.1
• 73232c0 [Dev Deps] update js-yaml
• 8a2d29b [Deps] update has, for-each, resolve, object-inspect
• c6f5313 [Tests] add eclint and eslint, to enforce a consistent style
• 45788a5 [Dev Deps] update concat-stream
• ec4a71d [fix] Fix bug in functionName regex during stack parsing
• 7261ccc Merge pull request #433 from mcnuttandrew/add-trb
• 6cbc53e Add tap-react-browser
• 9d501ff [Dev Deps] use ~ for dev deps; update to latest nonbreaking
• 24e0a8d Fix spelling of "parameterize"

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 Bot :palm_tree:

[greenkeeper[bot]]

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