rust-bitcoin

This is a routine automated update by Dependabot that bumps the version of a GitHub Actions helper used to download build artifacts in a daily fuzzing workflow. There is no code change to the rust-bitcoin library itself, and no security issue is indicated in the commit or supplied references.

This is a routine automated update by Dependabot that bumps the version of a GitHub-provided action used to upload security scan results. It changes only a pinned commit hash in a workflow file and does not alter the project's actual Bitcoin library code or introduce any vulnerability.

This commit only updates generated API snapshot text files to remove a constant named GENESIS_PREVIOUS_BLOCK_HASH from the public API listing. It does not change any actual Rust source code, so it cannot introduce or fix a security vulnerability on its own.

This commit simply removes an unused public constant from the WitnessCommitment type. It is a routine cleanup with no security implications.

This commit only updates generated API snapshot files that list the names of public types and functions. It renames error types like TryFromError to InvalidWitnessVersionError and FromStrError to ParseWitnessVersionError in those snapshots. There is no actual code change, no bug fix, and no security impact in this commit itself.

This commit is a simple renaming of error types in the rust-bitcoin library. It changes names like FromStrError to ParseWitnessVersionError and TryFromError to InvalidWitnessVersionError to match existing naming conventions. There is no change to program logic, no bug fix, and no security relevance.

This commit is a routine code cleanup in the rust-bitcoin library. It rewrites how optional amounts and fee rates are converted for JSON/serialization output to use more idiomatic Rust chaining (`.map(...).serialize(s)`) instead of explicit `match` blocks. There is no change to the actual serialized data or to security behavior.

This commit is a straightforward code cleanup in the rust-bitcoin library. It replaces deeply nested match blocks with newer, cleaner Rust syntax (let-else statements) inside safe arithmetic helper functions. The actual behavior of the code—checking for overflow and returning None on error—does not change. There is no security vulnerability being fixed here.

This commit simply deletes the project's optional Git hooks and the documentation and helper scripts that installed them. Git hooks are local developer convenience scripts that run on your own machine when you commit or merge code. Removing them does not change any shipped code, network behavior, or cryptographic logic, and it does not create a security vulnerability.

This commit updates the project's continuous integration (CI) setup for cross-compilation testing. It removes a custom Docker image and configuration, and instead installs a specific newer version of the 'cross' tool directly from its GitHub repository. There is no change to the actual Bitcoin library code that users run.

This commit is a routine cleanup of test code in the rust-bitcoin project's `units` crate. It renames test functions, reorganizes them, and adds clearer comments linking them to Rust API guideline conventions. There is no change to the actual library code that users depend on, and nothing in the commit suggests a security fix or vulnerability.

This commit is a routine cleanup of test code in the rust-bitcoin project. It renames test functions, adds comments, and reorganizes API surface tests to follow project conventions. There is no change to the actual library code that handles Bitcoin data, so it cannot introduce a security vulnerability or fix one.

This commit only renames and reorganizes test code in a single API test file. It adds compile-time checks that certain public types implement standard Rust traits like Debug, Send, Sync, serde, and Arbitrary. There is no change to production code, no bug fix, and no security relevance.

This commit only renames test functions and updates comments in a single Rust test file. It makes no changes to actual library code, behavior, or security-sensitive logic.

This commit only edits a documentation file (docs/policy.md). It adds coding guidelines and a table of contents for the project. There are no code changes, no bug fixes, and no security-related modifications.

This commit only renames existing test functions and adds one new internal policy test to verify that a public type implements the Arbitrary trait when the optional 'arbitrary' feature is enabled. It does not change any production code, cryptographic logic, network handling, or security behavior.

This commit only renames and recomments test functions in a single Rust test file. It does not change any production code, library behavior, or security-sensitive logic. There is no security issue here.

This commit simply deletes a GitHub Actions workflow file that automatically created GitHub releases when new version tags were pushed. It is a routine CI/infrastructure change with no code changes and no apparent security relevance.

This commit adds the ability to clone boxed versions of two custom unsized byte-wrapping types used in Bitcoin scripts. Before this change, code that tried to clone a Box<Script> or Box<PushBytes> would fail to compile. The change is a normal API completeness fix and does not appear to fix any memory-safety bug or security vulnerability.

This commit only changes a code comment. It replaces a developer TODO note with a short explanation that the code is verbose because it implements a state machine. No code behavior, logic, or security properties changed.

This commit is a routine release preparation: it bumps the version number of the `bitcoin-primitives` crate from 0.102.0 to 0.103.0, updates related dependency declarations in other crates, refreshes lock files, and adds a changelog entry. There are no code logic changes and no security fix or vulnerability introduced in the diff itself.

This is a routine dependency version bump in a Rust package manifest. The bitcoin crate was already using a feature ('hex') from its internal encoding crate, but the manifest only required version 1.0.0. Since that feature was added in version 1.1.0, the requirement is being corrected to 1.1.0. There is no security-relevant code change here.

This is a routine automated update that changes the pinned stable Rust compiler version in the project's configuration file from 1.96.0 to 1.97.1. It does not modify any source code, dependencies, or security-sensitive settings. There is no indication of a security fix or vulnerability.

This commit is a routine dependency update for the project's fuzz testing setup. It bumps the version of the 'bitcoin' crate used in fuzz tests from 0.32.101 to 0.32.102 and updates the corresponding lock files. There are no code changes to the library itself, and nothing in the commit suggests a security fix or vulnerability.

This commit only adds a new unit test. It does not change any production code, so it cannot by itself introduce or fix a security vulnerability. The test verifies that an invalid 'sendcmpct' network message (with a mode byte other than 0 or 1) is rejected during decoding. If the underlying code already rejects such messages, the test merely documents that behavior. If it did not, the test would fail and the vulnerability would remain unfixed.