rust-bitcoin

This is a routine automated update by Dependabot that bumps the version of a GitHub Actions helper used to save build artifacts in three CI workflow files. There is no indication of a security issue in the project code itself, and the change does not alter how the project handles Bitcoin data, keys, or network messages.

This is a routine automated update by Dependabot that bumps the version of a GitHub Actions workflow helper (actions/labeler) used to automatically label pull requests. There is no indication of a security issue in the change itself, and no evidence of malicious code in the referenced version.

This commit only updates generated API snapshot files to reflect that two existing types now expose a new public helper method called builder(). No actual source code changes are included, and there is no indication of a security fix or vulnerability.

This commit is a straightforward internal cleanup in the rust-bitcoin library. It replaces verbose pairs of encoders (a length counter plus a raw slice/bytes encoder) with new combined 'prefixed' encoder types that do the same job. There is no change to the actual bytes produced on the wire, no new behavior exposed to users, and no indication of a security bug being fixed.

This commit only updates generated API snapshot files (text listings of public types and methods). It does not change any source code, behavior, or fix any bug. There is no security relevance.

This commit changes a single sentence in the crate's documentation. It clarifies that the base58 crate requires an allocator specifically for decoding, not for all operations. There is no code change and no security impact.

This commit only updates generated API listing files (text snapshots of public functions/types). It adds lines describing two new public methods on script types. There is no source code change, no bug fix, and no security relevance visible in the diff.

This commit only updates automatically-generated API snapshot text files. The snapshots now show that some error and I/O types are reported as coming from Rust's `core` library instead of the `std` library. This is a documentation/test-artifact change with no functional code modification and no security relevance.

This is a routine patch-version update of a GitHub-maintained security scanning helper (the CodeQL upload-sarif action) inside a CI workflow. It does not change the project's actual Bitcoin library code, its public interfaces, or how user funds or data are handled. There is no indication this commit fixes or introduces a security vulnerability.

This is a routine update by Dependabot to the GitHub Action used for creating releases. It changes the pinned version of ncipollo/release-action from 1.20.0 to 1.21.0 in the project's release workflow. There is no direct evidence in the commit or supplied references that this update fixes a security vulnerability or introduces one. It is a normal dependency maintenance change.

This is a routine automated update by Dependabot that changes the pinned version of a GitHub Action used to install the 'uv' Python tool in two workflow files. The new version is a major release of the setup-uv action, but the commit itself only updates the pinned commit hash and keeps the same major-version comment. There is no indication in the commit that this fixes a security vulnerability or introduces malicious behavior.

This is a routine automated update by Dependabot that bumps the version of a GitHub Actions caching tool used only in a daily fuzzing workflow. There is no code change to the rust-bitcoin library itself, and nothing in the commit indicates a security problem.

This commit only updates generated API snapshot text files to reflect a function renaming (adding '_decoder' suffix to several decode helper functions). It changes no source code, logic, or behavior. There is no security relevance.

This commit only updates a documentation file that shows the project's internal dependency tree. No program code was changed, so it cannot introduce or fix a security vulnerability on its own.

This commit adds a new public helper function called decode_from_hex_with to a Rust Bitcoin encoding library. It is a pure feature addition that mirrors existing decode helpers and gives callers a way to decode hex strings by specifying a decoder type directly, rather than through an existing Decode trait. There is no bug fix, no change to existing behavior, and no security relevance in the code itself.

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, similar to a table of contents. No actual source code, logic, or behavior changed. The additions simply record two new helper functions that were already added elsewhere in the project. There is no security issue here.

This commit only updates two generated API listing files (text snapshots of public functions and types). It records that several new script helper methods, such as checking whether a script is a pay-to-public-key-hash or pay-to-witness-public-key-hash output, are now part of the public API. There is no actual code change, no bug fix, and no security-related content in the commit message or diff.

This commit simply deletes two unused internal constant definitions (SEGWIT_MARKER and SEGWIT_FLAG) from one source file because identical copies already exist elsewhere in the project. It is a routine code cleanup with no functional or security change.

This commit only updates generated API snapshot files that list what types and functions are publicly exposed by the library. The actual code did not change; only the recorded API signatures were updated to reflect new type aliases (shorter names for encoder combinations). There is no security issue here.

This is a small internal code cleanup in the rust-bitcoin library. It changes how transaction output (TxOut) objects are prepared for serialization so they use a dedicated wrapper type (TxOutEncoder) instead of directly combining two lower-level encoders. The commit message frames this as improving encapsulation, but the diff itself does not show any actual security bug, exploit path, or behavior change in the serialized output. It is best treated as a defensive maintenance patch.

This is a small internal code cleanup in the rust-bitcoin library. It changes how transaction input (TxIn) objects are prepared for serialization so they use a dedicated wrapper type (TxInEncoder) instead of a generic three-field encoder. The commit message frames this as better encapsulation, but the diff itself only shows a refactor with no change to the actual serialized bytes or to public behavior. There is no direct evidence of a security vulnerability being fixed.

This commit only updates an automatically generated API listing file. It reflects a change in how an error type is declared in the source code (from a public enum to a public struct wrapper), but the commit itself does not contain any actual code changes, logic changes, or security fixes. There is no indication this is a security patch.

This commit is a routine API design change, not a security fix. It renames an internal error enum and wraps it in a private struct so the library can keep the error type flexible before its first stable release. No vulnerability is patched and no exploit is possible.

This commit only updates internal fuzz-testing code to use a newer serialization API (consensus_encoding) instead of an older one being removed. It does not change the library's runtime behavior or fix any security bug.

This commit only updates three text files that list the public API surface of the `bitcoin_hashes` crate. It records two newly added methods (`hash` and `with_input`) on the `HashEngine` trait. There are no code changes, no bug fixes, and no security-sensitive behavior introduced by this commit itself.