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 ut_metadata is breaking the build 🚨 #1306

Closed
greenkeeper bot opened this issue Feb 21, 2018 · 1 comment
Closed

An in-range update of ut_metadata is breaking the build 🚨 #1306

greenkeeper bot opened this issue Feb 21, 2018 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

@greenkeeper greenkeeper bot commented Feb 21, 2018

Version 3.1.0 of ut_metadata was just published.

Branch Build failing 🚨
Dependency ut_metadata
Current Version 3.0.11
Type dependency

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

ut_metadata 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/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 10 commits.

  • ef43f53 sauce: drop android
  • bed0e36 travis: node lts
  • 79ef8e4 3.1.0
  • 8bc4d72 Merge pull request #28 from webtorrent/greenkeeper/bitfield-2.0.0
  • 6355779 fix(package): update bitfield to version 2.0.0
  • 2a39a8f remove greenkeeper badge
  • 5aeaca0 Merge pull request #25 from webtorrent/greenkeeper/initial
  • 9f78fc7 Update README.md
  • 76362ff docs(readme): add Greenkeeper badge
  • ebfcb7d chore(package): update dependencies

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 greenkeeper bot added the greenkeeper label Feb 21, 2018
@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Feb 21, 2018

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

@feross feross closed this Feb 21, 2018
@lock lock bot locked as resolved and limited conversation to collaborators May 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.