search

vladimir-barsuchenko / angular-tuned

2 stars 0 forks source link

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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 6 years ago

Version 1.7.3 of compression was just published.

Branch Build failing 🚨
Dependency compression
Current Version 1.7.2
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, 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 is in progress [Details](https://travis-ci.org/levgaas/angular-tuned/builds/404230931?utm_source=github_status&utm_medium=notification) - ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/levgaas/angular-tuned/242?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Release Notes 1.7.3
  • deps: accepts@~1.3.5
    • deps: mime-types@~2.1.18
  • deps: compressible@~2.0.14
    • Mark all XML-derived types as compressible
    • deps: mime-db@'>= 1.34.0 < 2'
  • deps: safe-buffer@5.1.2
Commits

The new version differs by 22 commits.

  • becc1c0 1.7.3
  • 2742fe9 docs: fix threshold documentation to match implementation
  • fd7a4d4 deps: safe-buffer@5.1.2
  • 5bca5aa deps: compressible@~2.0.14
  • c43c578 build: eslint-plugin-standard@3.1.0
  • 6160662 build: eslint-plugin-promise@3.8.0
  • d3c8269 build: eslint-plugin-import@2.13.0
  • 7ebf291 build: eslint-plugin-import@2.11.0
  • b3f7aa5 build: eslint@4.19.1
  • 363cbf6 build: Node.js@9.11
  • 5fe805f build: Node.js@8.11
  • 45eac05 build: Node.js@6.14
  • b1ecb6e build: Node.js@4.9
  • 2ce6799 tests: use after module for flow control
  • 52fa9c1 tests: fix backpressure tests

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