chore: bump go-waku #5150
Merged
chore: bump go-waku #5150
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
|
|
Jenkins BuildsClick to see older builds (8)
|
richard-ramos
force-pushed
the
bumpgo_waku-
branch
from
f4de41c
to
602efe2
Compare
|
|
richard-ramos
force-pushed
the
bumpgo_waku-
branch
from
602efe2
to
0df2111
Compare
|
|
kaichaosun
approved these changes
May 14, 2024
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.
During today's chatsdk PM call, we agreed to split #5123 into two separate PRs, one dealing with bumping go-waku, and another one dealing with storev3 upgrades.
That way, we can use latest go-waku in status-go without having to worry about storev3 being available in the fleet