search

gucong3000 / FELS

Front End Live Stream
MIT License
12 stars 4 forks source link

An in-range update of body-parser is breaking the build 🚨 #869

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 1.18.3 of body-parser was just published.

Branch Build failing 🚨
Dependency body-parser
Current Version 1.18.2
Type dependency

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

body-parser 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 failed [Details](https://travis-ci.org/gucong3000/FELS/builds/378835693?utm_source=github_status&utm_medium=notification)
Release Notes 1.18.3
  • Fix stack trace for strict json parse error
  • deps: depd@~1.1.2
    • perf: remove argument reassignment
  • deps: http-errors@~1.6.3
    • deps: depd@~1.1.2
    • deps: setprototypeof@1.1.0
    • deps: statuses@'>= 1.3.1 < 2'
  • deps: iconv-lite@0.4.23
    • Fix loading encoding with year appended
    • Fix deprecation warnings on Node.js 10+
  • deps: qs@6.5.2
  • deps: raw-body@2.3.3
    • deps: http-errors@1.6.3
    • deps: iconv-lite@0.4.23
  • deps: type-is@~1.6.16
    • deps: mime-types@~2.1.18
Commits

The new version differs by 32 commits.

  • e6ccf98 1.18.3
  • 0f75d30 Fix stack trace for strict json parse error
  • dde88eb build: support Node.js 10.x
  • d828f6d tests: remove "new Buffer" from tests
  • 036de9a deps: raw-body@2.3.3
  • c533873 deps: iconv-lite@0.4.23
  • db78a97 build: Node.js@9.11
  • 8201ede deps: qs@6.5.2
  • cfeeb59 build: eslint-plugin-import@2.11.0
  • d045949 build: safe-buffer@5.1.2
  • 6cb164b build: eslint-plugin-standard@3.1.0
  • 70815be deps: type-is@~1.6.16
  • 2653fc5 build: eslint-plugin-import@2.10.0
  • 55a2488 deps: http-errors@~1.6.3
  • f2959f5 lint: apply standard 11 style

There are 32 commits in total.

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] commented 6 years ago

After pinning to 1.18.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.