Skip to content
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

Merged
merged 3 commits into from
Jul 26, 2023
Merged

update go-libp2p to v0.29.0 #10001

merged 3 commits into from
Jul 26, 2023

Conversation

marten-seemann
Copy link
Member

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.

@marten-seemann marten-seemann requested review from lidel and a team as code owners June 27, 2023 16:31
@marten-seemann marten-seemann force-pushed the update-libp2p-v0281 branch 2 times, most recently from 64b0ce1 to d65efdb Compare June 27, 2023 16:43
@p-shahi p-shahi mentioned this pull request Jun 27, 2023
27 tasks
core/commands/id.go Show resolved Hide resolved
@marten-seemann
Copy link
Member Author

All tests are passing excpet for sharness. Can you take care of that one @Jorropo?

@Jorropo
Copy link
Contributor

Jorropo commented Jun 28, 2023

I'll

@hacdias hacdias requested a review from Jorropo June 29, 2023 11:07
@Jorropo Jorropo force-pushed the update-libp2p-v0281 branch 2 times, most recently from 24c030e to b0d926b Compare June 29, 2023 13:51
@marten-seemann
Copy link
Member Author

@Jorropo Any chance we can get this PR landed any time soon?

@MarcoPolo MarcoPolo changed the title update go-libp2p to v0.28.1 update go-libp2p to v0.29.0 Jul 14, 2023
@MarcoPolo
Copy link
Contributor

Updated to v0.29.0

@BigLep
Copy link
Contributor

BigLep commented Jul 14, 2023

Thanks. We will get this in before the 0.22 RC on 2023-07-20.

@marten-seemann
Copy link
Member Author

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.

@BigLep BigLep mentioned this pull request Jul 20, 2023
@Jorropo Jorropo force-pushed the update-libp2p-v0281 branch 2 times, most recently from b375758 to 2bbb278 Compare July 21, 2023 19:11
Copy link
Contributor

@Jorropo Jorropo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thx

@Jorropo Jorropo enabled auto-merge (rebase) July 21, 2023 19:11
@Jorropo
Copy link
Contributor

Jorropo commented Jul 21, 2023

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.

Agreed thx, I am merging as two commits within one PR.

docs/changelogs/v0.22.md Outdated Show resolved Hide resolved
@Jorropo Jorropo disabled auto-merge July 26, 2023 12:18
Co-authored-by: Jorropo <jorropo.pgm@gmail.com>
@Jorropo Jorropo enabled auto-merge (rebase) July 26, 2023 12:41
@Jorropo Jorropo merged commit 6be6630 into master Jul 26, 2023
14 checks passed
@Jorropo Jorropo deleted the update-libp2p-v0281 branch July 26, 2023 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

4 participants