An in-range update of formidable is breaking the build 🚨
Closed this issue · 2 comments
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 1.2.0 of formidable was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | formidable |
| Current Version | 1.1.1 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
formidable 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
Commits
The new version differs by 13 commits.
02fe171Bump5987b8cSimplify buffering in JSON parser23a8526Merge pull request #460 from xunleif2e/mastera248bbcFix OctetStreamtmp upload file cleanup while req aborted6041695Merge pull request #455 from Vitaha/master5ddd6d3Fix using closed _writeStream when error is occurred (#357)c7e47cdRevert "to solve EISDIR error (#424)"cee52d1Merge pull request #443 from leipert/patch-1549d7f0Remove duplicate license field from package.jsoncebe5edMerge pull request #439 from gswalden/patch-16b99fabupdate readme to reflect current state of Express05e4743to solve EISDIR error (#424)b81d1c7Added max upload size for files (#357)
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 🌴
After pinning to 1.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.