Skip to content
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

An in-range update of http-status-codes is breaking the build 🚨 #303

Open
greenkeeper bot opened this issue Mar 6, 2019 · 3 comments
Open

An in-range update of http-status-codes is breaking the build 🚨 #303

greenkeeper bot opened this issue Mar 6, 2019 · 3 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Mar 6, 2019

The dependency http-status-codes was updated from 1.3.0 to 1.3.1.

🚨 View failing branch.

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

http-status-codes 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).

Commits

The new version differs by 3 commits.

  • 338aa64 Bump patch version and publish
  • 3821d30 Added the http statuses as an enum. (#29)
  • 427963b Update README.md

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
Author

greenkeeper bot commented Mar 6, 2019

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

@greenkeeper
Copy link
Author

greenkeeper bot commented Mar 16, 2019

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

  • edd12d3 Bump patch version
  • 4420b72 Revert "Added the http statuses as an enum. (#29)"

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Oct 27, 2019

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

See the full diff

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