rust-bitcoin

This commit is a routine update to the project's release automation. It removes an old shell script used for release checks and replaces it with a new tool called cargo-rbmt. There are no changes to the actual Bitcoin library code, no bug fixes, and no security-related changes.

This commit is a routine cleanup of the project's automated testing configuration file. It merges several nearly identical test job definitions into two simpler, matrix-based job definitions. There is no change to the actual Bitcoin library code, no change to permissions or secrets, and no security relevance.

This is a routine maintenance change to the project's automated testing setup. It replaces a custom GitHub Actions helper with an equivalent upstream action and updates the version of an internal tool (cargo-rbmt). There is no change to the actual Bitcoin library code that users run, and nothing in the commit suggests a security problem or fix.

This commit simply moves a file called 'stable-version' from one folder to another within the project's CI configuration. The file contains a Rust compiler version number used by automated checks. There is no change to the project's actual Bitcoin code, no security fix, and no vulnerability introduced.

This commit changes a GitHub Actions workflow so that a security linting tool called zizmor is installed at a fixed version (1.22.0) instead of the latest release. It is a routine CI maintenance change to prevent unexpected breakages when zizmor releases new versions. There is no indication it fixes or introduces a security vulnerability.

This commit adds a new way to encode and decode Bitcoin peer-to-peer 'version' messages in the rust-bitcoin library. It is a routine refactoring and feature addition: it introduces a new encoder/decoder implementation and updates one test to use the new code. There is no indication of a security bug being fixed.

This commit adds a single Rust lint suppression to a macro that generates encoder helper types. It tells the Clippy static-analysis tool to stop complaining about overly complex types when nested encoders are combined. There is no functional code change, no bug fix, and no security relevance.

This is a minor code cleanup commit. It removes an unnecessary intermediate variable, updates a doc comment to match a previous API change, and removes an outdated comment in a test. There is no functional change and no security impact.

This commit adds convenience methods so that a Bitcoin keypair can sign messages directly, without callers having to reach into the underlying secp256k1 library. It is a code-cleanup and API-ergonomics change, not a fix for a known bug or vulnerability. The new methods wrap the same underlying signing functions that were already being used, so the cryptographic behavior is unchanged.

This commit is a routine code cleanup and feature addition. It adds new helper functions for reading small and medium-sized unsigned integers (u16 and u64) from hexadecimal strings, using the same safe approach already used for u32 and u128. There is no indication of a security bug being fixed or introduced.

This commit changes how the library exposes a Bitcoin secret key pair internally. Previously, calling `to_inner()` made a full copy of the secret key data. The new `as_inner()` returns a reference instead, so the secret bytes are not duplicated in memory as often. This is a defensive hardening change: it reduces the number of copies of sensitive key material floating around in memory, which slightly lowers the chance that a secret key could leak through memory dumps, swap, or debugging. It is not a fix for an active bug or a directly exploitable vulnerability.

This commit only updates a generated text file listing the public API surface of the crate. It adds four new public methods for converting Bitcoin scripts to/from hex strings. There is no code change, no bug fix, and no security relevance visible in the diff.

This commit simply moves an existing unit test from one file to another within the same project. It does not change any production code, fix a bug, or alter behavior. There is no security relevance.

This commit only adds a new unit test for existing script hex parsing and formatting functions. It does not change any production code, fix any bug, or alter behavior. There is no security relevance.

This is a routine internal code reorganization. It moves two helper functions that convert Bitcoin scripts to hexadecimal strings from the main `bitcoin` crate into the lower-level `primitives` crate. The functions still behave the same way; they are just located in a different module. There is no security fix or vulnerability here.

This commit is a routine code reorganization: it moves functions that parse Bitcoin script hex strings from the main `bitcoin` crate into the lower-level `primitives` crate. The old functions in `bitcoin` are kept as deprecated aliases so existing code keeps working. There is no security fix or vulnerability here.

This commit simply moves existing unit tests from two separate files into a single shared test file. It does not change any production code, behavior, or security logic. There is no security impact.

This is a tiny code cleanup change inside unit tests. It replaces `alloc::format!` with the shorter `format!` because the macro is already available in the test module. There is no functional change and no security relevance.

This commit only renames test functions in a single test file so the names match the project's preferred spelling (script_buf instead of scriptbuf). No code behavior changes, no security relevance.

This commit simply moves existing automated tests from one file to another within the project's source code. It does not change any actual program logic, fix bugs, or alter behavior. There is no security relevance.

This commit removes redundant Rust feature gates inside a module that is already entirely gated behind the 'alloc' feature. It is a code cleanup change with no security relevance.

This commit swaps out the old way of turning hex strings into Bitcoin scripts for a newer, more stable set of libraries. It also introduces a clearer error type so callers can tell whether something went wrong with the hex string itself or with decoding the script. The change is described by the project as a hardening/cleanup move, not a fix for a known vulnerability.

This is a routine code-maintenance change. The developers replaced one way of reading hexadecimal strings with another, because the old helper tool (the `FromHex` trait) is being removed in an upcoming version of a dependency. The function being changed is already marked as deprecated, so it is not the preferred way to do things. There is no indication this fixes a security bug or introduces a vulnerability.

This commit simply removes two outdated lines from a code comment. The removed text incorrectly claimed that the function always sets an even parity, but the function actually accepts a parity argument supplied by the caller. There is no code change and no security issue.

This commit is a routine dependency cleanup. It removes the external hex_lit crate and switches test/example code to use built-in hex macros from the project's own hex-conservative crate. There is no user-facing behavior change and no security fix or vulnerability introduced.