chore: upgrade libp2p to 0.55.0 #2683
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maqi
force-pushed
the
chore-upgrade_libp2p_to_0.55.0
branch
2 times, most recently
from
be51f4d to
4006ec2
Compare
They introduced a new `connection_id` field on some of the their types and this required updating our references to those. For now, I opted to not use the field.
jacderida
force-pushed
the
chore-upgrade_libp2p_to_0.55.0
branch
from
4006ec2 to
0201862
Compare
jacderida
force-pushed
the
chore-upgrade_libp2p_to_0.55.0
branch
from
0201862 to
f363344
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
04c8a6f chore: upgrade libp2p to 0.55.0
They introduced a new
connection_idfield on some of the their types and this required updatingour references to those. For now, I opted to not use the field.
b627ec5 chore: remove u256 conversion after libp2p upgrade