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

[greenkeeper[bot]]

Version 3.3.0 of supertest was just published.

Branch	Build failing 🚨
Dependency	supertest
Current Version	3.2.0
Type	dependency

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

supertest 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/WFCD/warframe-hub/builds/425462968?utm_source=github_status&utm_medium=notification)).

---

Release Notes

v3.3.0

#509 - Fix #486, bug in _assertBody, switch to deepStrictEqual (thanks @mikelax)
#510 - Refactor test files to use const/let (thanks @rimiti)

Commits

The new version differs by 10 commits.

• e910e85 chore: Prepare for v3.3.0 release.
• bd864de Merge pull request #511 from visionmedia/bugfix-486-equal
• 101fbf5 Merge branch 'master' into bugfix-486-equal
• 04230bb Merge pull request #510 from visionmedia/refact-const-let
• 510a7ae bugfix: 486 Change method to use deepStrictEqual. (#509)
• 913150d chore(.editorconfig) [*.md] block removed
• 82e0828 refact(test/supertest.js) vars replaced by const and let
• 5443136 chore(.editorconfig) configuration file created
• 7233ba6 chore(.eslintrc) parserOptions option added to use es6
• 322ebf6 bugfix: 486 Change method to use deepStrictEqual.

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 3.2.0 your tests are passing again. Downgrade this dependency 📌.

[TobiTenno]

pinned to 3.2.0