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

[greenkeeper[bot]]

The dependency express was updated from 4.16.4 to 4.17.0.

🚨 View failing branch.

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

express 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/betamore/fswd-lab-6/builds/533604361?utm_source=github_status&utm_medium=notification)).

---

Release Notes for 4.17.0

• Add express.raw to parse bodies into Buffer
• Add express.text to parse bodies into string
• Improve error message for non-strings to res.sendFile
• Improve error message for null/undefined to res.status
• Support multiple hosts in X-Forwarded-Host
• deps: accepts@~1.3.7
• deps: body-parser@1.19.0
  • Add encoding MIK
  • Add petabyte (pb) support
  • Fix parsing array brackets after index
  • deps: bytes@3.1.0
  • deps: http-errors@1.7.2
  • deps: iconv-lite@0.4.24
  • deps: qs@6.7.0
  • deps: raw-body@2.4.0
  • deps: type-is@~1.6.17
• deps: content-disposition@0.5.3
• deps: cookie@0.4.0
  • Add SameSite=None support
• deps: finalhandler@~1.1.2
  • Set stricter Content-Security-Policy header
  • deps: parseurl@~1.3.3
  • deps: statuses@~1.5.0
• deps: parseurl@~1.3.3
• deps: proxy-addr@~2.0.5
  • deps: ipaddr.js@1.9.0
• deps: qs@6.7.0
  • Fix parsing array brackets after index
• deps: range-parser@~1.2.1
• deps: send@0.17.1
  • Set stricter CSP header in redirect & error responses
  • deps: http-errors@~1.7.2
  • deps: mime@1.6.0
  • deps: ms@2.1.1
  • deps: range-parser@~1.2.1
  • deps: statuses@~1.5.0
  • perf: remove redundant path.normalize call
• deps: serve-static@1.14.1
  • Set stricter CSP header in redirect response
  • deps: parseurl@~1.3.3
  • deps: send@0.17.1
• deps: setprototypeof@1.1.1
• deps: statuses@~1.5.0
  • Add 103 Early Hints
• deps: type-is@~1.6.18
  • deps: mime-types@~2.1.24
  • perf: prevent internal throw on invalid type

Commits

The new version differs by 53 commits.

• 10c7756 4.17.0
• 9dadca2 docs: remove Gratipay links
• b8e5056 tests: ignore unreachable line
• 94e48a1 build: update example dependencies
• efcb17d deps: cookie@0.4.0
• b9ecb9a build: support Node.js 12.x
• 5266f3a build: test against Node.js 13.x nightly
• e502dde build: Node.js@10.15
• da6f701 deps: range-parser@~1.2.1
• 88f9733 deps: serve-static@1.14.1
• 8267c4b deps: send@0.17.1
• bc07a41 deps: finalhandler@~1.1.2
• c754c8a build: support Node.js 11.x
• e917028 build: Node.js@8.16
• 7b076bd build: Node.js@6.17

There are 53 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]]

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

[greenkeeper[bot]]

• The dependency express was updated from 4.17.0 to 4.17.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• e1b45eb 4.17.1
• 0a48e18 Revert "Improve error message for null/undefined to res.status"
• eed05a1 build: Node.js@12.3

See the full diff