-
Notifications
You must be signed in to change notification settings - Fork 0
An in-range update of supertest is breaking the build 🚨 #60
Comments
After pinning to 3.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 3.2.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv3.2.0
CommitsThe new version differs by 29 commits.
There are 29 commits in total. See the full diff |
Version 3.3.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv3.3.0#509 - Fix #486, bug in _assertBody, switch to CommitsThe new version differs by 10 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v3.4.0
CommitsThe new version differs by 14 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 9 commits.
See the full diff |
Version 3.1.0 of supertest was just published.
supertest
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
Release Notes
v3.1.0Commits
The new version differs by 1 commits.
d4a63af
Release v3.1.0 (#474)
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 🌴
The text was updated successfully, but these errors were encountered: