8000 An in-range update of http-errors is breaking the build 🚨 · Issue #102 · zeekay/bebop · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

An in-range update of http-errors is breaking the build 🚨 #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
greenkeeper bot opened this issue Jun 24, 2019 · 1 comment
Open

An in-range update of http-errors is breaking the build 🚨 #102

greenkeeper bot opened this issue Jun 24, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor
greenkeeper bot commented Jun 24, 2019

The dependency http-errors was updated from 1.7.2 to 1.7.3.

🚨 View failing branch.

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

http-errors 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).

Commits

The new version differs by 18 commits.

  • a91d0ad 1.7.3
  • 1e23295 build: eslint-plugin-import@2.18.0
  • 1cb6101 build: eslint-plugin-node@8.0.1
  • 3ee0789 deps: inherits@2.0.4
  • 80035a1 build: support Node.js 12.x
  • 6d617c3 build: migrate to Travis CI trusty image
  • accb47c build: Node.js@11.15
  • 06a3b83 build: Node.js@10.16
  • b47b476 build: Node.js@8.16
  • 5ff8559 build: Node.js@6.17
  • 7328d0b build: simplify & speed up logic in Travis CI build steps
  • 30516ba build: mocha@6.1.4
  • 631611d build: eslint-plugin-promise@4.1.1
  • ecff0a9 build: eslint-plugin-import@2.17.3
  • 2b91170 build: eslint@5.16.0

There are 18 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
Copy link
Contributor Author
greenkeeper bot commented Jun 24, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants
0