Conversation
- peer-store from libp2p git - gossipsub from sigp git - the rest from crates.io
jking-aus
approved these changes
Mar 18, 2025
This file contains hidden or 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
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.
This PR updates our dependencies. This is grouped into commits for easier review:
anchorbranch of Lighthouse 🥳. This includes goodies like the tracing PR and fixes for the CVEs that have been breaking CI.peer-store(which is not on crates.io yet) andgossipsub(which we get from the SigP fork).cargo update": Ranscargo updateto get all the trivially updatable versions.alloy,derive_more,strum": These were easily updatable without code changes being necessary.randwhere possible": Updatesrandto 0.9.0, except inbls_lagrange, because our dependencies there are still on0.8.5. I think it is worth having two versions in the dependency graph here, because then our move to 2024 edition of Rust will be cleaner (as 0.9 avoids collision with the new reserved keywordgen).