chore(deps): bump dig-gossip -> v0.13.0 (#1517 connect-leg fix)#81
Merged
Conversation
Consumes dig-gossip v0.13.0 (tag commit 5bb335360ee1): pool auto-dial now threads the discovered peer_id into the mTLS SPKI pin (no zero-pin) and dials the full NAT ladder incl. the relay circuit after Direct fails. dig-node already builds the relayed dialer + attaches RelayStatus, so this is a pure git-rev bump of the peer-stack exception dependency — no node logic change. Bumps chia-protocol / chia-sdk-client vendored-fork [patch.crates-io] revs and the dig-gossip git dep to the same v0.13.0 tag commit; Cargo.lock relocked (dig-gossip 0.12.0 -> 0.13.0). Workspace version 0.53.0 -> 0.54.0. Enables #1062 Leg B relayed-connect e2e re-run against dig-node main. Co-Authored-By: Claude <noreply@anthropic.com>
MichaelTaylor3d
marked this pull request as ready for review
July 22, 2026 22:42
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
1 participant
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.
What
Bumps dig-node's
dig-gossipgit dependency (the peer-stack exception — git-rev, NOT crates.io) from v0.12.0 (e6ea13e6a090) to v0.13.0 (tag commit5bb335360ee16a856b217b429f205eead31dee80), the #1517 connect-leg fix.dig-gossip v0.13.0 makes pool auto-dial thread the discovered
peer_idinto the mTLS SPKI pin (no zero-pin) and dial the full NAT ladder incl. the relay circuit after Direct fails.Changes
Cargo.toml[patch.crates-io]:chia-protocol+chia-sdk-clientvendored-fork revs → v0.13.0 tag commit.crates/dig-node-core/Cargo.toml:dig-gossipgit rev → v0.13.0 tag commit (+ doc comment refreshed).Cargo.lockrelocked: dig-gossip 0.12.0 → 0.13.0 (chia-protocol/chia-sdk-client rehung on new rev).Blast radius
Pure dependency-rev bump of the peer-stack exception. Per the #1517 diagnosis, dig-node already builds the relayed dialer + attaches
RelayStatus, so no node logic change was required. The new dig-gossip surface is additive — the full workspace builds and all tests pass with zero call-site adaptation.How verified
cargo build --workspace— green (dig-gossip v0.13.0 compiled).cargo test --workspace— green, 0 failing suites.Why
Enables the #1062 Leg B relayed-connect e2e to re-run against dig-node
main(built from source on EC2) = the flywheel-connect acceptance. Part of the dig-node establishment epic / #1517.