What the developer wrote
Authored by Tobin C. Harding
units: Correctly group deps
By convention optional dependencies are grouped separately to
non-option ones.
What changed, and why it matters
This commit is purely cosmetic: it moves one optional dependency line down by one position in a configuration file so that optional and non-optional dependencies are grouped separately, matching project convention. There is no code change and no security relevance.
No action needed; this is a non-security formatting/style change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff in units/Cargo.toml reorders the ‘encoding’ dependency to appear after ‘internals’ so that non-optional dependencies are grouped before optional ones. No version, feature, path, or functional configuration is changed.
Changed components
units/Cargo.tomlInspect captured patch +1 / −1
diff --git a/units/Cargo.toml b/units/Cargo.toml
index 29ffbd8c..1b700df8 100644
--- a/units/Cargo.toml
+++ b/units/Cargo.toml
@@ -18,9 +18,9 @@ std = ["alloc", "internals/std", "encoding?/std"]
alloc = ["internals/alloc", "serde?/alloc", "encoding?/alloc"]
[dependencies]
-encoding = { package = "bitcoin-consensus-encoding", path = "../consensus_encoding", version = "=1.0.0-rc.3", default-features = false, optional = true }
internals = { package = "bitcoin-internals", path = "../internals", version = "0.5.0" }
+encoding = { package = "bitcoin-consensus-encoding", path = "../consensus_encoding", version = "=1.0.0-rc.3", default-features = false, optional = true }
serde = { version = "1.0.195", default-features = false, features = ["derive"], optional = true }
arbitrary = { version = "1.4.1", optional = 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.