libp2p / js-peer-info

libp2p Peer abstraction Node.js implementation
https://libp2p.io
MIT License
37 stars 28 forks source link

An in-range update of peer-id is breaking the build 🚨 #50

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 0.8.7 of peer-id just got published.

Branch Build failing 🚨
Dependency peer-id
Current Version 0.8.6
Type dependency

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

As peer-id is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:


Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/libp2p/js-peer-info/builds/218047563) - ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/libp2p/js-peer-info/153?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Commits

The new version differs by 4 commits .

  • af6575d chore: release version v0.8.7
  • ccf0b78 chore: update contributors
  • 733b40b Merge pull request #60 from libp2p/feat/update-keys
  • ac27907 feat: set privKey pubKey

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree: