Skip to content

An in-range update of formidable is breaking the build 🚨 #11

@greenkeeper

Description

@greenkeeper

☝️ 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
  • bitHound - Code 2 failing files. Details
  • bitHound - Dependencies 2 failing dependencies. Details

Commits

The new version differs by 13 commits.

  • 02fe171 Bump
  • 5987b8c Simplify buffering in JSON parser
  • 23a8526 Merge pull request #460 from xunleif2e/master
  • a248bbc Fix OctetStreamtmp upload file cleanup while req aborted
  • 6041695 Merge pull request #455 from Vitaha/master
  • 5ddd6d3 Fix using closed _writeStream when error is occurred (#357)
  • c7e47cd Revert "to solve EISDIR error (#424)"
  • cee52d1 Merge pull request #443 from leipert/patch-1
  • 549d7f0 Remove duplicate license field from package.json
  • cebe5ed Merge pull request #439 from gswalden/patch-1
  • 6b99fab update readme to reflect current state of Express
  • 05e4743 to solve EISDIR error (#424)
  • b81d1c7 Added 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 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions