-
Notifications
You must be signed in to change notification settings - Fork 286
update libp2p branch when unstable changes #6202
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
base: unstable
Are you sure you want to change the base?
Conversation
cb75ed2
to
efeb1c9
Compare
- name: Update libp2p branch | ||
run: | | ||
cd vendor/nim-libp2p | ||
git checkout unstable |
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.
needs updating for the new naming scheme
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.
done
Is this still relevant? We are still running Libp2p nodes but they are outdated and Holesky fork is today:
I guess I can update the branch manually for now. |
Updated manually for today:
|
Co-authored-by: tersec <tersec@users.noreply.github.com>
31f5a9a
to
239dedf
Compare
a0510ce
to
aa88cd4
Compare
ping @richard-ramos is this still relevant? |
in nim-libp2p we’ve got this workflow that bumps the autobump branch with the latest unstable from nimbus + latest master from nim-libp2p whenever something lands in nim-libp2p master. this new one looks basically the same but triggers on changes to nimbus unstable. not clear what extra value it adds, feels redundant since the existing one already covers the same ground from the nim-libp2p side, so i vote to close this PR |
This PR automates updating the libp2p branch when the Nimbus unstable branch changes. The libp2p branch will contain the latest Nimbus and nim-libp2p unstable.