Closed greenkeeper[bot] closed 5 years ago
Update to this version instead π
The new version differs by 12 commits.
cc6785f
chore: release version v0.9.0
ca287fb
chore: update contributors
4d4163d
test: always use Connection instances for tests
74f6fd8
test: check if we dialed to the right peer
ee1f64c
test: add more interesting benchmarks
d26590d
test: make tests go faster, way faster
5ee1573
refactor: speed up benchmarks
65b9675
chore: fix linting
87fb346
chore: update ignore files
09312b1
chore: update dependencies, including latest aegir and CI
a5d10ca
Merge pull request #94 from libp2p/automatic-ci-script-update
1d9f6af
Updating CI files
See the full diff
Update to this version instead π
Update to this version instead π
The new version differs by 6 commits.
00d1f54
chore: release version v0.9.4
ed2c86e
chore: update contributors
7e44e45
chore: update deps
6d09b47
fix: pass the handshake failure on
0e23874
test: add test for handshake to expose error bubbling issue
b6e1baa
refactor: clean up callbacks to avoid naming collision
See the full diff
dependency
libp2p-secio was updated from 0.6.8
to 0.10.1
.
Version 0.7.0 of libp2p-secio just got published.
The version 0.7.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of libp2p-secio. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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: