rust-bitcoin

This commit is a routine internal code reorganization. It moves a helper method, is_coinbase, from one module to another within the same project. The method's logic and behavior are unchanged, and there is no indication of a security fix or vulnerability.

This commit is a routine internal code reorganization. It moves the existing Merkle tree helper trait and transaction identifier abstraction from the main `bitcoin` crate into the lower-level `primitives` crate, and adds public wrapper functions and tests. The actual Merkle root calculation logic is copied verbatim, with no functional change.

This commit is a small API cleanup, not a security fix. It changes a Bitcoin data-encoding helper so it accepts ordinary memory sizes (usize) instead of a special internal type. The only behavioral change is on hypothetical future 128-bit computers, where impossibly large values would be encoded as the maximum allowed u64 value. On all current systems the output is unchanged.

This commit is a routine code-quality improvement. It marks a number of simple constructor and getter functions as 'const', which lets the Rust compiler evaluate them at compile time. There is no change to what the functions do, no bug fix, and no security-relevant behavior change.

This commit is a routine code-quality improvement. It marks several simple constructor and getter functions as 'const', meaning they can be evaluated at compile time. There is no change to program logic, no bug fix, and no security relevance.

This commit only adds two new unit tests to verify that two decoder types allocate memory in correctly-sized batches. It does not change any production code, fix a bug, or alter behavior. There is no security-relevant change.

This commit is a routine code cleanup in the rust-bitcoin library. It replaces hand-written ceiling-division logic with Rust's newer built-in `div_ceil` function. The math result is intended to be identical, and there is no indication of a security bug being fixed.

This commit only adds formatting hints to test code so that a code formatter (rustfmt) leaves byte arrays arranged in tidy 8-byte columns. It does not change any behavior, logic, or security-sensitive code.

This commit is a routine maintenance update to the project's fuzz-testing infrastructure. It adds newly-created fuzz test targets to a script that auto-generates configuration files, and refreshes the generated files to match. There is no change to the actual Bitcoin library code that users rely on, and no security fix or vulnerability is present.

This commit is a one-character typo fix in the changelog, changing 'paramater' to 'parameter'. It does not modify any source code, build scripts, tests, or documentation that affects how the software behaves.

This commit is a routine API cleanup: it changes custom I/O traits in the rust-bitcoin project so they can be used with Rust's dynamic-dispatch feature ('dyn'). The code changes are purely about making the traits more flexible for downstream users. There is no indication in the commit or title that this fixes a security vulnerability, and the diff does not change any security-critical behavior such as bounds checking, parsing limits, or cryptographic validation.

This commit fixes a bug in how the rust-bitcoin library decodes Bitcoin transactions that have no inputs. Normally, the library uses a special encoding for zero-input transactions. The decoder was incorrectly trying to read witness data even when there were no inputs, which would cause decoding to fail. The fix skips witness decoding when there are no inputs, and a new test verifies that an empty transaction can be encoded and decoded correctly.

This commit is a straightforward internal code cleanup. It removes a temporary 36-byte buffer and manual byte copying when decoding an OutPoint (a Bitcoin transaction reference), replacing it with a direct split of the already-decoded byte array. There is no security-relevant change.

This commit only adds a new documentation file describing which versions of the rust-bitcoin library are considered long-term support (LTS) and which dependency versions correspond to each release. No code was changed, and there is no security fix or vulnerability present.

This commit is a routine code cleanup: it turns on a Rust linter warning for unnecessary .clone() calls and removes those unnecessary clones. There is no security-relevant behavior change.

This commit only adds a new unit test to the codebase. It does not change any production code, fix a bug, or alter behavior. The test verifies that a decoding function correctly ignores extra bytes after the expected data when reading from a stream. There is no security issue present in the commit itself.

This commit only adds new unit tests for a decoder that reads length-prefixed byte vectors. It does not change any production code, so it cannot introduce or fix a runtime security vulnerability by itself. The tests verify that the decoder stops exactly at the declared payload length and does not accidentally consume extra trailing bytes.

This commit is a routine code-quality cleanup. It turns on a Rust linter rule (clippy::use_self) that encourages using 'Self' instead of repeating a type's name inside its own implementation blocks, and updates the affected code to satisfy the new rule. There is no functional change, no bug fix, and no security relevance.

This commit is a code-style cleanup in the rust-bitcoin library's units crate. It enables a Clippy lint called use_self and replaces explicit type names (like FeeRate, Weight, LockTime) with the shorthand Self inside impl blocks. These changes do not alter program behavior, fix no bugs, and have no security relevance.

This commit only turns on a Rust style lint (clippy::use_self) and replaces explicit type names with `Self` in the source code. It does not change what the code does, only how it is written. There is no security impact.

This commit is a routine performance and ergonomics improvement. It changes several Rust constructor functions from regular functions to 'const' functions, which lets the compiler precompute some values at compile time rather than runtime. There is no change to security behavior, no bug fix, and no vulnerability patch.

This commit swaps in a newer, stable version of a helper library (hex-conservative 1.0.0) for public-facing parts of the rust-bitcoin 'primitives' crate, while keeping the older version for internal-only uses. It is a dependency/API-stability cleanup, not a fix for a known security bug. There is no direct evidence in the commit that it addresses an exploit or vulnerability.

This is a routine dependency update by Dependabot that bumps the GitHub Actions 'upload-artifact' action from version 4 to version 5 in three internal workflow files. There is no code change to the rust-bitcoin library itself, and nothing in the commit suggests a security problem or fix.

This is a routine automated update by Dependabot that bumps a GitHub Actions helper (used to download build artifacts) from version 5 to version 6 in a daily fuzzing workflow. There is no indication of a security vulnerability or malicious change in the commit itself.

This commit is a routine code-style cleanup. It changes some function return type declarations from explicit type names (like `TxOut` or `CompactTarget`) to `Self` inside Rust extension traits. This has no effect on what the functions do or on security.