rust-bitcoin

This commit is a code-quality maintenance change. It adds pattern-matching destructuring inside Rust error-type 'source' methods that previously just returned 'None'. The goal is to make the compiler warn future maintainers if the shape of an error type changes, so they remember to update the source() implementation. It does not change runtime behavior, fix a bug, or close a security vulnerability.

This commit is a routine performance optimization. It changes one function so that it decodes a hex string directly into the final data structure instead of first creating a temporary byte buffer and then copying it. There is no security-relevant change visible in the diff.

This commit is purely a code-style cleanup. It rearranges public re-exports of external crates in the units library to match the project's preferred grouping and alphabetical ordering. No functionality, behavior, or security properties change.

This commit simply removes a duplicate compiler warning-suppression directive from a Rust source file. The same suppression is already set in the project's shared configuration file, so the change has no functional effect and no security relevance.

This commit is a routine release-preparation change. It bumps the version number of the `bitcoin_hashes` crate from 0.21.0 to 1.0.0, updates the changelog, and updates dependency references in lock files and other crates' configuration files. There are no code changes and no security relevance.

This is a small performance improvement for fuzz testing code. It changes how random Bitcoin P2P command strings are generated during fuzzing, avoiding a temporary String allocation. There is no security issue visible in the change.

This commit is a routine automated code-formatting run by the rustfmt tool. It only changes whitespace, line breaks, and import grouping in six files. No program logic, security checks, or behavior were altered.

This commit narrows the visibility of an internal field inside an error type from public to crate-internal. It is a routine API-cleanup change with no security relevance.

This commit only updates generated API text files to reflect that two error types now implement a standard Rust conversion from the Infallible type. Infallible is a type that can never actually exist, so this change adds no real behavior and cannot cause security problems. It is a documentation-like update for the public API listing.

This commit is a documentation-only cleanup. It removes a stale reference in a code comment to a type parameter (`HashEngine::BYTES`) that had already been removed from the code. No executable code was changed, and there is no security impact.

This commit is a pure code cleanup: it renames an internal helper macro from `engine_input_impl!` to `impl_engine_input!` and switches its syntax from parentheses to curly braces. No logic, behavior, or security properties of the hashing code change.

This commit adds compiler hints to three small functions in the rust-bitcoin hashes crate, suggesting the compiler should inline them. It does not change behavior, fix a bug, or address any security issue.

This commit adds a standard Rust trait implementation that lets two error types be automatically converted from the 'Infallible' type (a type that can never actually exist). It is a routine ergonomic improvement and does not fix any security bug or change runtime behavior.

This commit only adjusts whitespace indentation inside a Rust macro definition. It does not change any program logic, behavior, or security properties.

This commit is a pure rename of an internal Rust macro from `serde_impl!` to `impl_serde_traits!` to match the project's naming convention. No code behavior changes; it is a cosmetic refactoring.

This commit removes a single blank line from a Rust source file. It is a cosmetic formatting change with no functional effect on the code.

This commit is a one-line documentation fix that adds a missing macro name to a list in a code comment. It does not change any executable code, behavior, or security properties.

This commit only rewrites internal documentation comments inside a Rust source file. No executable code, logic, or behavior changed. It is purely a formatting and wording cleanup of doc comments.

This commit only changes the wording of code comments (documentation) from singular verbs like 'Finalize' to plural verbs like 'Finalizes' to match the project's style convention. No actual program code was modified, so it cannot affect security or behavior.

This commit simply removes a handful of Rust compiler/clippy lint configuration lines from a source file. The same lint settings are already present in the project's central configuration, so this is a cleanup change with no effect on program behavior or security.

This commit only updates documentation comments in a single Rust source file. It rewords explanations, adds a forward-compatibility note, and removes an embedded shell example from the docs. No code logic, function signatures, or behavior changed.

This commit only adds new automated tests that verify the public API surface of the bitcoin-network-kind crate. It does not change any production code, fix bugs, or alter behavior. There is no security relevance.

This commit is purely a build and release hygiene change. It turns on two automated checks for the `network` crate—one that verifies the crate's public API surface before release, and one that validates pre-release metadata. It also adds the generated API snapshot files to the crate's exclusion list so they are not accidentally published. There is no change to runtime code, no bug fix, and no security-relevant behavior change.

This commit adds two small Rust trait implementations that allow certain error types to be automatically converted from the 'Infallible' type. 'Infallible' is a type that can never actually exist, so these conversions are purely for making the error types easier to use in generic code. There is no security issue here.

This is a small internal code cleanup in the Bitcoin peer-to-peer networking code. It removes an unnecessary memory copy when converting text into a command string used in network messages. There is no security bug being fixed here.