An in-range update of supertest-fetch is breaking the build 🚨

[greenkeeper]

The devDependency supertest-fetch was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

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

supertest-fetch 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).

---

Release Notes for v1.2.1

1.2.1 (2018-09-17)

Bug Fixes

• Fix to handle case when passed in server is bound to a UNIX domain socket. (dddfd29), closes #15

Commits

The new version differs by 1 commits.

• dddfd29 fix: Fix to handle case when passed in server is bound to a UNIX domain socket.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[greenkeeper]

• The devDependency supertest-fetch was updated from 1.2.1 to 1.2.2.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for v1.2.2

1.2.2 (2018-09-17)

Bug Fixes

• Move @types/express from dev dependencies to dependencies. (a71b9b5)

Commits

The new version differs by 1 commits.

• a71b9b5 fix: Move @types/express from dev dependencies to dependencies.

See the full diff

[jwalton]

🎉 This issue has been resolved in version 1.0.7 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀