sletjs / slet-plugin-static

static server plugin with gizp/etag/serve
https://github.com/sletjs/slet-plugin-static
MIT License
1 stars 0 forks source link

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

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.1.0 of koa-compress was just published.

Branch Build failing 🚨
Dependency koa-compress
Current Version 2.0.0
Type dependency

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

koa-compress 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/sletjs/slet-plugin-static/builds/366407834?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 20 commits ahead by 20, behind by 1.

  • d4a6db7 2.1.0
  • fe36555 travis: sudo false
  • 542c73f do not compress if response is not writable (#71)
  • 049e9de test: switch to jest
  • 6459d56 :arrow_up: bytes@3
  • d30bf9a readme: add codecov badge
  • baf4096 lint
  • 2f60047 test: switch to codecov
  • 34c0fff travis: only test 8 & stable
  • f80ec15 readme: update travis badge
  • c61aa06 chore(package): update should to version 13.0.1 (#64)
  • a1dd956 Update dependencies to enable Greenkeeper 🌴 (#63)
  • e50d15f test: flush=Z_SYNC_FLUSH
  • 740cd44 travis: test node@8
  • 9fdf774 chore(package): update should to version 11.2.1 (#59)

There are 20 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 2.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.