rust-bitcoin

This commit simply moves existing proof-of-work serialization tests from one crate to another within the same project. It is a test-only refactoring change with no effect on production code or security.

This commit is a small internal cleanup in the Rust Bitcoin library. It replaces a hand-written string-splitting routine used when reading a 256-bit number from hexadecimal text with a call to an existing library function that does the same thing. There is no indication this fixes a bug or security issue; it is a code-quality refactor.

This commit removes an unused code path from the deserialization logic for a 256-bit unsigned integer type (U256). The removed code handled raw byte input, but the surrounding code only ever asks serde for a string, so the byte path was unreachable. There is no security fix here—just cleanup of dead code.

This commit is a simple code relocation: it moves the implementation of serde serialization/deserialization for the U256 type from one internal file to another, without changing the actual logic. There is no security-relevant change visible in the diff.

This commit is a routine internal cleanup in the Rust Bitcoin library. It removes some automatic error-conversion shortcuts (called `From` implementations) for two hex-parsing error types and replaces their uses with explicit constructor calls. There is no indication this fixes a security bug; it is a normal API-refactoring change.

This commit only updates generated API snapshot text files. It removes lines that listed certain error-conversion functions from the public API surface, but it does not change any actual Rust source code, logic, or behavior. There is no security issue visible in this commit.

This commit is a code cleanup inside the rust-bitcoin library. It moves the logic for parsing 256-bit unsigned integers from hexadecimal strings into a shared internal module, without changing what the library exposes to users. The change is purely internal refactoring.

This commit only updates automatically-generated API snapshot files. It records that two error types in the proof-of-work module moved from one public path to another (e.g., bitcoin_units::pow::ParseTargetError to bitcoin_units::pow::error::ParseTargetError). There is no actual code change, no bug fix, and no security-relevant behavior change in this commit itself.

This commit is a routine internal code cleanup in the rust-bitcoin library. It moves two error types (ParseTargetError and ParseWorkError) from a macro-generated location into a dedicated error submodule and re-exports them. The change does not alter parsing behavior, security checks, or public API functionality; it only reorganizes where the error types are defined and slightly adjusts their error messages to use a consistent internal helper.

This commit is a purely cosmetic code cleanup. It moves a public re-export statement to the top of a source file so the file is better organized. There is no functional change, no bug fix, and no security relevance.

This commit is an automated code-formatting run by rustfmt. It only reorders an import statement and removes a trailing space in a test line. There is no functional change to the program.

This is a routine automated update that changes one line in the project's configuration file, bumping the pinned Rust nightly compiler version from March 27, 2026 to April 10, 2026. There is no code change, no bug fix, and no security-relevant content.

This commit changes only a fuzz-testing helper shell script. It adds a configuration entry telling an internal lint tool (rbmt) that the crate 'hex-conservative' is allowed to appear as a duplicate dependency in the fuzz workspace. There is no change to production code, no cryptographic logic, no network handling, and no user-facing behavior. It is not a security fix and does not introduce a security issue.

This commit adds a new automated fuzz-testing target for Partially Signed Bitcoin Transactions (PSBTs) in the rust-bitcoin project. It does not change production behavior, fix a bug, or alter any user-facing API. It only adds test infrastructure and small helper implementations needed to generate random PSBT-like objects for fuzzing. The fuzz target itself even documents a pre-existing known panic condition it works around, rather than fixing it.

This commit adds a GitHub Actions workflow that automatically opens or closes a repository issue when two specific scheduled CI workflows (Fuzz and Kani CI) fail or succeed on the master branch. It is purely an automation/notification change and does not modify any library code, cryptography, network handling, or user-facing behavior of the rust-bitcoin crate.

This commit only adds #[inline] hints to small, simple functions in the rust-bitcoin units crate. It is a performance-oriented code-quality change with no functional or security impact.

This commit only updates generated API snapshot text files in the rust-bitcoin repository. These files list what functions and types are publicly exposed by the library, but they are not source code. The deletions show that some internal helper types and a debug function are no longer part of the public API, which is a normal cleanup or refactoring outcome. There is no code change, no bug fix, and no security issue visible in this commit.

This commit only hides two internal helper items from the public API documentation. It does not change any code behavior, access permissions, or security boundaries. There is no security issue here.

This commit simply hides an internal data structure (called State) from outside users of the library. It is an API-cleanup change, not a security fix. There is no patch for a vulnerability and no indication of any exploit or unsafe behavior.

This commit only updates the text of an automated comment left by a GitHub workflow when an API-breaking change is detected. It changes the instructions so they point to the correct CI job name. There is no code change, no security fix, and no vulnerability.

This commit is a routine code reorganization. It moves several error type definitions from the main p2p crate file into a new dedicated error submodule, then re-exports them so existing code can still use them the same way. There is no functional change to how the library behaves.

This commit is a pure code reorganization: it moves error type definitions from the main message module into a new 'error' submodule and re-exports them so existing code keeps working. There are no functional changes to how messages are parsed, validated, or handled.

This commit is a pure code reorganization: it moves several error type definitions from the main message_blockdata module into a new error submodule and re-exports them. There are no functional changes to how errors are created, handled, or displayed, and no security behavior changes.

This commit is a straightforward internal code reorganization in the rust-bitcoin library. It moves several error type definitions from the main address module into a new error submodule and re-exports them so existing users are unaffected. There is no change to how addresses are parsed, validated, or handled, and no security fix or vulnerability is present.

This commit is a pure code reorganization: it moves several error type definitions from the main message_network.rs file into a new error submodule and re-exports them. There is no change to how the code behaves, no bug fix, and no security-relevant change.