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

[greenkeeper[bot]]

The dependency already was updated from 1.8.0 to 1.9.0.

🚨 View failing branch.

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

already is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

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

---

Release Notes for v1.9.0

1.9.0 (2019-07-03)

Bug Fixes

• warnings: Silenced an unhandled promise rejection warning (false positive) (7095797)

Features

• deferSet: Added deferSet feature (340b4ab)
• deps: Bumped throat to v5 (ee7adcc)

Commits

The new version differs by 7 commits.

• 340b4ab feat(deferSet): Added deferSet feature
• ee7adcc feat(deps): Bumped throat to v5
• 901133b test(system): Moved from mocha to jest
• 7095797 fix(warnings): Silenced an unhandled promise rejection warning (false positive)
• 67c2cd3 test(funnel): Added exception handling tests
• d0db197 docs(readme): Added dm badge and clarified meta functions
• 1e0401f test(upstream): Bumped nyc

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 1.8.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.