-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
update go-libp2p to v0.29.0 #10001
update go-libp2p to v0.29.0 #10001
Conversation
64b0ce1
to
d65efdb
Compare
d65efdb
to
446f2aa
Compare
6f79feb
to
ff36a73
Compare
All tests are passing excpet for sharness. Can you take care of that one @Jorropo? |
I'll |
ff36a73
to
35b8134
Compare
24c030e
to
b0d926b
Compare
@Jorropo Any chance we can get this PR landed any time soon? |
Updated to v0.29.0 |
Thanks. We will get this in before the 0.22 RC on 2023-07-20. |
Would it make sense to keep this two separate PRs, one updating to v0.28.x and the other one updating to v0.29.x? This would allow us to bisect, should there be any libp2p related problem. |
b375758
to
2bbb278
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thx
Agreed thx, I am merging as two commits within one PR. |
2bbb278
to
048f8e7
Compare
Co-authored-by: Jorropo <[email protected]>
d88eb86
to
f7af719
Compare
While we're planning to to ship v0.29.0 on time for the next release, I'd like to update to v0.28.1 early in the process, mostly to catch any potential regressions early, and to make sure that we at least get v0.28 in, in case the v0.29 release is delayed.