rust-bitcoin

This commit only updates a generated API snapshot file (all-features.txt). It records that some serde helper functions now require only Encode for serialization and only Decode for deserialization, rather than requiring both traits. The actual code change happened elsewhere; this file is just documentation/testing output. There is no security issue visible here.

This commit relaxes the rules for which Rust types can be converted to and from serde serialization formats. Previously, a type had to support both encoding and decoding to be used in either direction. Now, types only need to support the direction actually being used. This is a straightforward API improvement with no security-relevant behavior change.

This commit simply adds a new internal software building block (a Rust crate dependency called bitcoin-consensus-encoding) to another internal crate (taproot-primitives). It updates package lists and feature flags so the new dependency can be used in future work, but it does not change any actual logic, data handling, or security behavior. There is nothing here that directly fixes or introduces a vulnerability.

This commit only updates generated API snapshot text files that record which Rust traits are implemented for the library's types. The actual code change (adding or removing trait bounds on equality comparisons for a Block type) is not present in the diff; only the auto-generated documentation of the public API surface changed. There is no executable code modification, no bug fix, and no security-relevant behavior change visible here.

This is a routine automated update by Dependabot that bumps the version of a GitHub-owned action used to upload security scan results. It changes one pinned commit hash in a CI workflow file and does not alter any project code, cryptographic logic, or user-facing behavior. There is no indication this introduces or fixes a security vulnerability in the rust-bitcoin library itself.

This is a routine automated update by Dependabot that bumps a GitHub Actions helper (taiki-e/install-action) used in testing workflows from version 2.79.3 to 2.79.12. It only changes which version of the action is used to install Rust testing tools in CI. There is no indication this fixes or introduces a security issue in the rust-bitcoin library itself.

This commit only updates generated text files that list the public API of the crate. The change records that the Opcode type now implements the Hash trait, which is a normal, additive feature addition. There is no code change, no bug fix, and no security relevance visible in the diff.

This commit only updates generated API snapshot text files to reflect that a Rust formatting trait was added for a Bitcoin witness-version type. There is no code change, no bug fix, and no security relevance visible in the diff.

This commit is a routine Rust packaging change. It makes several internal dependency crates (base58, bech32, crypto, network, primitives, serde) publicly visible to users of the 'addresses' crate so that types from those crates can be used cleanly in the public API. There is no bug fix, behavior change, or security patch here.

This commit only updates generated API snapshot text files to reflect recent changes in public function signatures. It does not change any source code, fix bugs, or alter program behavior. There is no security relevance.

This commit is a routine API cleanup: it makes a few Bitcoin merkle-root functions accept a broader range of input types (generic iterators and borrowed transactions) instead of only slices or exact iterator types. There is no security bug being fixed and no behavior change for callers that already used the old API. The tests were updated only to remove unnecessary `.into_iter()` calls.

This commit only updates generated API text files to reflect that a Rust trait now requires an internal 'sealed' marker. It is a documentation or API-snapshot update with no code changes and no security relevance.

This is a routine Dependabot update that bumps a GitHub Actions helper (taiki-e/install-action) used in automated testing workflows to a newer minor version. It does not change the project's actual Bitcoin library code, its dependencies, or how user funds or data are handled. There is no security-relevant change visible in the commit.

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 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 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 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 only updates generated API snapshot files that record which types and functions are publicly visible in the library. No actual source code was changed, and nothing in the commit fixes or introduces a security problem. It is a routine housekeeping change.

This commit only updates generated API snapshot files to reflect that a new `extend` method was added to the `Witness` type. The actual code change happened elsewhere, and these files are just machine-generated documentation of the public API surface. There is no security issue visible in this commit itself.

This commit is a pure code-style refactor. It rewrites how error values are built so each wrapping step is on its own line instead of being nested inside a single expression. The actual error values produced and the program's behavior are unchanged. There is no security fix or vulnerability here.

This commit is a straightforward internal code cleanup. It removes duplicated error-handling code in three decoder 'end' methods and rewrites the logic using pattern matching and early returns. There is no change to what errors are produced or when they are produced; the behavior appears identical before and after.

This is a routine update by Dependabot that bumps the version of a GitHub Actions helper called actions/github-script from version 8.0.0 to 9.0.0 in two workflow files. The workflows only manage issue/label automation after CI runs and do not handle source code, secrets, or release artifacts. There is no indication in the commit that this fixes a security vulnerability.

This is a routine automated dependency update by Dependabot. It changes the version of a GitHub Action used to install a Rust tool during automated semver compatibility checks. There is no indication in the commit that this fixes or introduces any security issue.