consensus_encoding: Add dep version number
What the developer wrote
Authored by Tobin C. Harding
consensus_encoding: Add dep version number
Add a version number to the deps so we can publish.
What changed, and why it matters
This commit adds version numbers to two internal Rust package dependencies in a Cargo.toml file so the crate can be published to a package registry. It is a routine build/publishing configuration change with no security relevance.
No security action needed. Treat as normal maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies consensus_encoding/Cargo.toml to add explicit version fields (0.16.0 for bitcoin_hashes and 0.4.0 for bitcoin-internals) to path-based dependencies. This is required by crates.io for publishing but does not alter code behavior, dependency resolution in normal workspace builds, or any cryptographic or consensus logic.
Changed components
consensus_encoding/Cargo.tomlInspect captured patch +2 / −2
diff --git a/consensus_encoding/Cargo.toml b/consensus_encoding/Cargo.toml
index 48800fb6..9264565a 100644
--- a/consensus_encoding/Cargo.toml
+++ b/consensus_encoding/Cargo.toml
@@ -18,8 +18,8 @@ std = ["alloc", "internals/std"]
alloc = ["internals/alloc"]
[dependencies]
-hashes = { package = "bitcoin_hashes", path = "../hashes", default-features = false }
-internals = { package = "bitcoin-internals", path = "../internals" }
+hashes = { package = "bitcoin_hashes", path = "../hashes", version = "0.16.0", default-features = false }
+internals = { package = "bitcoin-internals", path = "../internals", version = "0.4.0" }
[package.metadata.docs.rs]
all-features = true
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.