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

[greenkeeper]

The dependency compression was updated from 1.7.3 to 1.7.4.

🚨 View failing branch.

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

compression 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).

---

Release Notes for 1.7.4

• deps: compressible@~2.0.16
  • Mark text/less as compressible
  • deps: mime-db@'>= 1.38.0 < 2'
• deps: on-headers@~1.0.2
  • Fix res.writeHead patch missing return value
• perf: prevent unnecessary buffer copy

Commits

The new version differs by 33 commits.

• dd5055d 1.7.4
• 7e91b18 perf: prevent unnecessary buffer copy
• f6873b5 build: supertest@4.0.0
• b07e7fd build: eslint-plugin-import@2.16.0
• aed82c0 build: eslint@5.15.1
• 5b7d4c0 build: mocha@6.0.2
• ddf2b6e build: simplify & speed up logic in Travis CI build steps
• 61a438d build: Node.js@11.10
• 7ee13e1 deps: on-headers@~1.0.2
• 8fb7dca deps: compressible@~2.0.16
• 77a22c6 build: Node.js@11.6
• 7d952de build: Node.js@10.15
• f5c4a57 build: Node.js@8.15
• 5a5ee57 build: Node.js@6.16
• edb43f3 build: eslint-plugin-markdown@1.0.0

There are 33 commits in total.

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 🌴

[greenkeeper]

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