refactor(crate): rename dig-protocol -> dig-peer-protocol (#1383) - #4
Merged
Merged
Conversation
Package rename only, no behaviour change. Bumps 0.2.0 -> 0.2.1 to clear the version-increment gate. Updates Cargo.toml package name + repository URL, lib.rs doc header, README/SPEC import examples, and fixes a copy-paste "dig-gossip" leftover in publish.yml's GitHub Release step (release name/body/install snippet/README link). Consumers (dig-gossip, dig-slashing) migrate their dependency name in follow-up PRs. The crate publishes to crates.io as a new package name dig-peer-protocol 0.2.1; the old dig-protocol package is yanked once consumers have moved. Refs #1383 Co-Authored-By: Claude <noreply@anthropic.com>
MichaelTaylor3d
marked this pull request as ready for review
July 21, 2026 14:08
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.
What changed
Package rename ONLY, no behaviour/API change:
Cargo.toml:name = "dig-protocol"->"dig-peer-protocol",version0.2.0 -> 0.2.1 (clears the version-increment gate on a name-only change),repositoryURL updated toDIG-Network/dig-peer-protocol.src/lib.rs: doc header + "consumers depend on X alone" line updated. Nodig_protocol::self-references existed (crate usescrate::), so nothing else insrc/changes.README.md/SPEC.md: crate-name references and thedig_protocol::{...}import example updated todig_peer_protocol. Everychia-protocol/chia_protocolreference and theDIG_MESSAGE= 220 text are untouched.CHANGELOG.md: new[0.2.1]entry documenting the rename..github/workflows/publish.yml: fixed a pre-existing copy-paste bug in thecreate-releasejob — it hardcoded "dig-gossip" (release name, body heading/description, install snippet, README link) instead of this crate's name. Now saysdig-peer-protocol. Secret names untouched.How verified
cargo build --no-default-features: PASS (aws-lc-sys/native-tls/rustls features fail to build in this checkout for an unrelated reason — a Windows MAX_PATH limit hit by aws-lc-sys's CMake TryCompile scratch dir under this deeply-nested worktree path; reproduced identically onmainbefore the rename viagit stash, confirming it's a pre-existing environment issue, not caused by this change).cargo test --no-default-features: 47/47 tests PASS (dig_message, dig_message_type, introducer_wire — decode/serde/error/round-trip coverage all green).cargo fmt --check: clean.cargo clippy --no-default-features -- -D warnings: clean.grep -rn "\bdig-protocol\b\|\bdig_protocol\b" . --include=*.rs --include=*.toml --include=*.md --include=*.yml(excluding target/.gitnexus) returns only the intentional CHANGELOG rename note.Follow-up (not in this PR)
dig-gossipanddig-slashingmigrate their dependency name todig-peer-protocolin separate follow-up PRs.dig-peer-protocol0.2.1 (orchestrator-owned); the olddig-protocolcrates.io package is yanked once consumers have moved. Repo rename on GitHub is also orchestrator-owned.Refs #1383