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

Version 1.7.1 of compression just got published.

Branch	Build failing 🚨
Dependency	compression
Current Version	1.7.0
Type	dependency

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 this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:

Status Details

- ❌ **bitHound - Dependencies** 4 failing dependencies. [Details](https://www.bithound.io/github/billymoon/monsieur/55fe41defada4add5b8c9e430380eae0140de154/dependencies/npm#filter-failing-dep) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/billymoon/monsieur/55fe41defada4add5b8c9e430380eae0140de154/files?status=passing)

Release Notes

1.7.1

deps: accepts@~1.3.4
- deps: mime-types@~2.1.16
deps: bytes@3.0.0
deps: compressible@~2.0.11
- deps: mime-db@'>= 1.29.0 < 2'
deps: debug@2.6.9
deps: vary@~1.1.2
- perf: improve header token parsing speed

Commits

The new version differs by 9 commits.

93586e7 1.7.1
bd3fa8a deps: bytes@3.0.0
e1ce980 deps: vary@~1.1.2
d0f7eab deps: debug@2.6.9
931c346 build: Node.js@8.4
8c8e36a deps: compressible@~2.0.11
8a5e773 deps: accepts@~1.3.4
7b4a7e2 build: eslint-plugin-node@5.1.1
de30e3a build: mocha@2.5.3

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

billymoon / monsieur

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

Version 1.7.1 of compression just got published.