rust-bitcoin

This commit only adds new unit tests for the existing hexadecimal encoding/decoding code. It does not change any production logic, so it cannot introduce or fix a security vulnerability on its own.

This commit is a simple internal code reorganization. It moves the SerializedLegacyPublicKey type from the main bitcoin crate into the lower-level crypto crate and re-exports it so existing code keeps working. No behavior changes, no bug fixes, and no security implications are visible in the diff.

This is a small internal code cleanup in the rust-bitcoin library. It changes how one public-key wrapper type exposes its underlying byte slice, removing a dependency on another type (PushBytes) so the code can be moved between crates more easily. There is no user-visible behavior change and no security fix.

This commit only updates version numbers and pinned commit hashes for GitHub Actions used in the project's automated CI (continuous integration) workflows. It does not change any of the actual Bitcoin library code that users or applications interact with. There is no indication of a security vulnerability being fixed or introduced.

This commit only updates automatically-generated API snapshot files. It shows a public type being renamed from EncodableByteIter to EncoderByteIter and changing from borrowing an encodable value to owning an encoder. There is no source code change in the diff, no bug fix, and no security-relevant behavior shown.

This is a routine internal refactoring of a Rust Bitcoin library type. It renames EncodableByteIter to EncoderByteIter and changes it to wrap an encoder directly rather than an encodable value. There is no security fix or vulnerability indicated in the commit.

This is a routine code cleanup commit that fixes two Rust lint warnings in the taproot-primitives crate. It adds a Clippy suppression annotation and replaces an integer cast with a safer conversion. There is no security-relevant behavior change.

This commit is a routine code reorganization: it moves Taproot hash types (like TapLeafHash, TapNodeHash, TapTweakHash) and the LeafVersion enum from the main bitcoin crate into a new taproot-primitives crate. The bitcoin crate then re-exports these types so existing users see no change. There is no security fix or behavior change visible in the diff.

This commit is a routine internal code reorganization. It moves some Taproot hash helper methods from direct implementations on two types into Rust 'extension traits' so the underlying types can live in a more basic crate while the extra logic stays in the main bitcoin crate. There is no change to what the code computes or any security behavior.

This commit creates a brand-new, empty Rust crate named 'bitcoin-taproot-primitives'. It contains no executable code, no new logic, and no changes to existing behavior. It is purely a project structure change preparing for future development.

This commit removes automatic error-conversion shortcuts in the crypto module of the rust-bitcoin library. It does not fix a bug or vulnerability; it is a deliberate API cleanup to avoid promising too much to future users. Existing code that relied on the removed conversions will need minor updates, but runtime behavior is unchanged.

This commit simply makes several existing key types easier to import by re-exporting them at the top level of the crypto crate. It does not change any behavior, logic, or security properties of the code.

This change simply re-exports a few internal Rust crates through the public API of the `crypto` sub-crate so users don't have to add those dependencies manually. It is a routine dependency-management and API-ergonomics patch with no apparent security relevance.

This commit simply moves existing transaction encoding and decoding tests from one file to another. It does not change any production code, only reorganizes test code. The only functional tweak is replacing one detailed error comparison with a broader pattern match, because the moved test can no longer see a private inner error type. There is no security issue here.

This commit is a large but straightforward internal code reorganization. It moves Bitcoin key types (public keys, private keys, keypairs, and related errors) from the main `bitcoin` crate into a new `crypto` sub-crate, then re-exports them so existing users of the `bitcoin` crate see the same public API. There is no indication of a security bug being fixed or introduced; it is a refactoring to improve the project's modular structure.

This commit is a routine version bump for an internal Rust crate. It changes the package version from 0.0.0 to 0.1.0, updates dependency references and lock files, and records the migration of code into the crate in the changelog. There are no code logic changes and no security-relevant behavior changes visible in the diff.

This commit only cleans up style warnings in a Rust source file. It replaces wildcard imports with explicit Self:: references, adds a documentation comment, and fixes a minor formatting issue in a doc comment. There is no change to program behavior or security.

This commit is a routine code reorganization: it moves some Bitcoin signature-hash type definitions (EcdsaSighashType, TapSighashType, and related error types) from the main bitcoin crate into a new bitcoin-crypto sub-crate, then re-exports them so existing users see no change. There is no functional change to how signatures or transactions are validated.

This commit is a simple internal code cleanup in the rust-bitcoin library. It moves two nearly identical helper functions into a shared internal trait, without changing what the code does or how it behaves. There is no security issue here.

This is a small code-quality change in how a Bitcoin-related Rust library reports parsing errors for a special sighash type. It makes the error message come directly from the underlying Taproot parser instead of being manually rebuilt. There is no direct security vulnerability here, but it slightly improves error-message accuracy and removes a tiny bit of duplicated logic.

This commit is a routine code cleanup in the rust-bitcoin crypto crate. It fixes compiler lint warnings by adding documentation comments, adjusting number formatting, and making minor style changes. There is no functional change to how signatures are created, validated, or parsed, and no security issue is present.

This commit is a routine internal code reorganization. It moves a low-level ECDSA signing helper method from the main PrivateKey implementation into a new extension trait called PrivateKeyExt, and updates the one place that uses it to import the trait. There is no change to what the code does or any security fix.

This commit is a routine internal code reorganization. It moves the ECDSA signature module from the main 'bitcoin' crate into a smaller 'crypto' sub-crate, then re-exports it so existing users see no change. There is no security fix or vulnerability here.

This commit is a routine internal code reorganization. It moves a few public-key helper methods into Rust 'extension traits' so the underlying key types can be relocated to a different crate later. The actual behavior of the moved functions is unchanged, and there is no indication of a bug fix or security patch.

This commit is a routine fix to the project's automated fuzz-testing pipeline. It adds an installation step for the 'cargo-fuzz' tool in one CI job and updates a script that generates the workflow file. There is no change to the actual Bitcoin library code that users depend on, and nothing in the commit suggests a security vulnerability or fix.