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

[greenkeeper]

The devDependency supertest was updated from 3.4.0 to 3.4.1.

🚨 View failing branch.

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

supertest 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

• ✅ ci/circleci: install: Your tests passed on CircleCI! (Details).
• ❌ ci/circleci: pkg-ok: Your tests are queued behind your running builds (Details).
• ❌ ci/circleci: testNext: Your tests are queued behind your running builds (Details).
• ❌ ci/circleci: test6: CircleCI is running your tests (Details).
• ❌ ci/circleci: test: CircleCI is running your tests (Details).
• ✅ ci/circleci: lint: Your tests passed on CircleCI! (Details).
• ❌ ci/circleci: audit: Your tests failed on CircleCI (Details).

---

Commits

The new version differs by 9 commits.

• 8ef3840 3.4.1
• cea9ff5 Merge pull request #535 from visionmedia/v3.4.1
• 013caf0 doc(History.md) changelog updated
• 0d4a6dc Merge pull request #533 from rimiti/publish-only-necessary
• 9ed4909 chore(package-lock.json) file updated
• c1a1c37 fix(test/supertest.js) test fixed, message has been updated
• 87756fb Revert "chore(test/supertest.js) obscure test removed"
• 9e6851b Revert "chore(test/supertest.js) obscure test removed"
• ad882c2 chore(.npmignore) only publish necessary files

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