An in-range update of multiaddr is breaking the build 🚨

[greenkeeper]

Version 2.2.2 of multiaddr just got published.

Branch	Build failing 🚨
Dependency	multiaddr
Current Version	2.2.1
Type	dependency

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

As multiaddr 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 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details

• ❌ ci/circleci Your tests failed on CircleCI Details

Commits

The new version differs by 4 commits .

• aeb7936 chore: release version v2.2.2
• c762154 chore: update contributors
• f56856d chore: update aegir and fix linting
• c2508b4 docs(readme): flat-square badges from shields.io

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 2.2.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 5 commits .

• d632745 chore: release version v2.2.3
• 1939b35 chore: update contributors
• cbfcbdb chore: update deps
• 08d5d5d [WIP] feat: adding p2p-circuit proto (#41)
• e7e53b9 test: use dirty-chai

See the full diff.

[greenkeeper]

Version 2.3.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits .

• 1ff2328 chore: release version v2.3.0
• d0b6174 chore: update contributors
• ec23f14 feat: don't throw on invalid b58 string in getPeerId (#43)

See the full diff.