Public commit record
45/100 · Thin
What the developer wrote
Authored by jrakibi
hashes: update API text files
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
What changed, and why it matters
This commit only updates three generated API snapshot text files so that the documented type aliases for HkdfSha256 and HkdfSha512 point to HashEngine instead of Hash. These are documentation/snapshot files used to track the public API surface; they contain no executable code changes and no security fix or vulnerability.
Recommended action
No security action needed. Treat as routine API-snapshot maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies hashes/api/all-features.txt, hashes/api/alloc-only.txt, and hashes/api/no-features.txt. In each file the type alias lines for HkdfSha256 and HkdfSha512 are updated from bitcoin_hashes::hkdf::Hkdf
Changed components
hashes/api/all-features.txthashes/api/alloc-only.txthashes/api/no-features.txtInspect captured patch +6 / −6
diff --git a/hashes/api/all-features.txt b/hashes/api/all-features.txt
index 752d9abd..ae171c35 100644
--- a/hashes/api/all-features.txt
+++ b/hashes/api/all-features.txt
@@ -1910,8 +1910,8 @@ pub fn bitcoin_hashes::drain_to_engine<T, H>(encoder: &mut T, engine: &mut H) wh
pub fn bitcoin_hashes::drain_to_hash<T, H>(encoder: &mut T) -> <H as bitcoin_hashes::HashEngine>::Hash where T: bitcoin_consensus_encoding::encode::Encoder + ?core::marker::Sized, H: bitcoin_hashes::HashEngine + core::default::Default
pub fn bitcoin_hashes::encode_to_engine<T, H>(object: &T, engine: &mut H) where T: bitcoin_consensus_encoding::encode::Encode + ?core::marker::Sized, H: bitcoin_hashes::HashEngine
pub fn bitcoin_hashes::encode_to_hash<T, H>(obj: &T) -> <H as bitcoin_hashes::HashEngine>::Hash where T: bitcoin_consensus_encoding::encode::Encode + ?core::marker::Sized, H: bitcoin_hashes::HashEngine + core::default::Default
-pub type bitcoin_hashes::HkdfSha256 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha256::Hash>
-pub type bitcoin_hashes::HkdfSha512 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha512::Hash>
+pub type bitcoin_hashes::HkdfSha256 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha256::HashEngine>
+pub type bitcoin_hashes::HkdfSha512 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha512::HashEngine>
pub type bitcoin_hashes::HmacSha256 = bitcoin_hashes::hmac::Hmac<bitcoin_hashes::sha256::Hash>
pub type bitcoin_hashes::HmacSha512 = bitcoin_hashes::hmac::Hmac<bitcoin_hashes::sha512::Hash>
pub type bitcoin_hashes::Sha256t<T> = bitcoin_hashes::sha256t::Hash<T>
\ No newline at end of file
diff --git a/hashes/api/alloc-only.txt b/hashes/api/alloc-only.txt
index 67e04f9c..7bcccbc3 100644
--- a/hashes/api/alloc-only.txt
+++ b/hashes/api/alloc-only.txt
@@ -1685,8 +1685,8 @@ pub fn bitcoin_hashes::drain_to_engine<T, H>(encoder: &mut T, engine: &mut H) wh
pub fn bitcoin_hashes::drain_to_hash<T, H>(encoder: &mut T) -> <H as bitcoin_hashes::HashEngine>::Hash where T: bitcoin_consensus_encoding::encode::Encoder + ?core::marker::Sized, H: bitcoin_hashes::HashEngine + core::default::Default
pub fn bitcoin_hashes::encode_to_engine<T, H>(object: &T, engine: &mut H) where T: bitcoin_consensus_encoding::encode::Encode + ?core::marker::Sized, H: bitcoin_hashes::HashEngine
pub fn bitcoin_hashes::encode_to_hash<T, H>(obj: &T) -> <H as bitcoin_hashes::HashEngine>::Hash where T: bitcoin_consensus_encoding::encode::Encode + ?core::marker::Sized, H: bitcoin_hashes::HashEngine + core::default::Default
-pub type bitcoin_hashes::HkdfSha256 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha256::Hash>
-pub type bitcoin_hashes::HkdfSha512 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha512::Hash>
+pub type bitcoin_hashes::HkdfSha256 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha256::HashEngine>
+pub type bitcoin_hashes::HkdfSha512 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha512::HashEngine>
pub type bitcoin_hashes::HmacSha256 = bitcoin_hashes::hmac::Hmac<bitcoin_hashes::sha256::Hash>
pub type bitcoin_hashes::HmacSha512 = bitcoin_hashes::hmac::Hmac<bitcoin_hashes::sha512::Hash>
pub type bitcoin_hashes::Sha256t<T> = bitcoin_hashes::sha256t::Hash<T>
\ No newline at end of file
diff --git a/hashes/api/no-features.txt b/hashes/api/no-features.txt
index 53e4ca01..cf5276f0 100644
--- a/hashes/api/no-features.txt
+++ b/hashes/api/no-features.txt
@@ -1562,8 +1562,8 @@ pub fn bitcoin_hashes::drain_to_engine<T, H>(encoder: &mut T, engine: &mut H) wh
pub fn bitcoin_hashes::drain_to_hash<T, H>(encoder: &mut T) -> <H as bitcoin_hashes::HashEngine>::Hash where T: bitcoin_consensus_encoding::encode::Encoder + ?core::marker::Sized, H: bitcoin_hashes::HashEngine + core::default::Default
pub fn bitcoin_hashes::encode_to_engine<T, H>(object: &T, engine: &mut H) where T: bitcoin_consensus_encoding::encode::Encode + ?core::marker::Sized, H: bitcoin_hashes::HashEngine
pub fn bitcoin_hashes::encode_to_hash<T, H>(obj: &T) -> <H as bitcoin_hashes::HashEngine>::Hash where T: bitcoin_consensus_encoding::encode::Encode + ?core::marker::Sized, H: bitcoin_hashes::HashEngine + core::default::Default
-pub type bitcoin_hashes::HkdfSha256 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha256::Hash>
-pub type bitcoin_hashes::HkdfSha512 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha512::Hash>
+pub type bitcoin_hashes::HkdfSha256 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha256::HashEngine>
+pub type bitcoin_hashes::HkdfSha512 = bitcoin_hashes::hkdf::Hkdf<bitcoin_hashes::sha512::HashEngine>
pub type bitcoin_hashes::HmacSha256 = bitcoin_hashes::hmac::Hmac<bitcoin_hashes::sha256::Hash>
pub type bitcoin_hashes::HmacSha512 = bitcoin_hashes::hmac::Hmac<bitcoin_hashes::sha512::Hash>
pub type bitcoin_hashes::Sha256t<T> = bitcoin_hashes::sha256t::Hash<T>
\ No newline at end of file
Risk score
Our methodology →Why this scored 15/100
Human-validated context
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
No validated notes yet.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.