-
Notifications
You must be signed in to change notification settings - Fork 247
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
chore: bump go-libp2p, go-waku and golang #4601
Conversation
|
Jenkins BuildsClick to see older builds (42)
|
|
|
@richard-ramos @cammellos : issue is fixed on status-mobile side, I'll run E2E and have QA look at this next week and then after that lets merge this. |
|
e344471
to
cc55e75
Compare
|
1 similar comment
|
9bf5df8
to
5ffec68
Compare
|
5ffec68
to
2db5b0b
Compare
|
1 similar comment
|
5bedae1
to
0c79a22
Compare
|
0c79a22
to
3ba8010
Compare
|
Can we merge this? |
Hi @richard-ramos : it was discussed recently that this and its corresponding status-mobile PR can be merged in a week after the current release testing is done |
Hi @richard-ramos! How critical it would be to merge this PR after cutting release go branch? We would prefer not to risk before release. I guess we will need another week before release branch is cut. |
It's not critical. Let's wait after release. We can still use the older go version with no problems. |
3ba8010
to
1c9ff57
Compare
|
1c9ff57
to
1c1b9ea
Compare
|
2 similar comments
|
|
0947a22
to
f3b1cb7
Compare
|
|
closing in favour of : #5027 |
This PR attempts to bump
uses the same code which was reverted in : #4522
status-mobile PR to test : status-im/status-mobile#18564
status: ready