rust-bitcoin

This commit changes a GitHub Actions workflow so that an 'API break' label is added when a version-compatibility check fails and removed when it passes. Previously the label was only added and a comment was always posted. There is no security issue visible in this change.

This is an automated code-formatting commit from rustfmt. It only removes blank lines between imports and wraps one long function call across multiple lines. There are no security changes.

This commit fixes the project's daily automated fuzzing test job. It adds an explicit installation step for the cargo-fuzz tool, ensures the script uses bash so error handling works correctly, and fixes a shell variable expansion quirk so custom Rust compiler flags don't break when unset. There is no change to the library code that users depend on, and no security vulnerability is present or patched.

This commit only updates generated API snapshot text files to reflect that the remainder (modulo) operator for the Weight type now returns another Weight instead of a plain number. It contains no source code changes, no bug fix, and no security-related content.

This commit only adds a new unit test. It checks that dividing and taking the remainder of a Weight value can be reversed to get the original value. No code behavior is changed, and no security issue is introduced or fixed.

This commit is a small type-correctness fix for the Rust Bitcoin library. It changes the result type of the remainder operator (%) when both inputs are Weight values, so the result is a Weight instead of a plain number. This is a normal API cleanup, not a security fix.

This commit only changes documentation comments in the consensus_encoding crate. It renames descriptions like 'Primitive decoders' to 'Primitive and combinator decoder types' and updates several function doc comments to say 'consensus decodable type' instead of 'object'. No code logic, signatures, or behavior changed. There is no security impact.

This commit only rewrites the user-facing documentation comments in a single Rust source file. It clarifies how the consensus encoding library works and reorganizes the description of provided functions. No program logic, APIs, or security behavior changed.

This commit only changes documentation comments in a Rust Bitcoin library. It clarifies that certain encoding functions and types are specifically tied to Bitcoin consensus encoding rules. No code behavior was changed, so there is no security impact.

This commit is a routine internal refactoring in the rust-bitcoin SHA-256 hashing code. It exposes the SHA-256 initial value (IV) as a public constant and renames an internal helper function so it can start from any midstate rather than always starting fresh. There is no security bug or fix here—just a code cleanup and API preparation for future const-context hashing features.

This commit adds new helper methods to the SHA-256 'Midstate' type in the rust-bitcoin hashes library. These helpers let callers compute SHA-256 intermediate states inside 'const' contexts (compile-time constants). It is a routine feature addition with no obvious security bug, no fix of a vulnerability, and no disclosed security relevance.

This commit only updates three text files that list the public API surface of the `bitcoin_hashes` crate. It adds entries for newly exposed SHA-256 midstate methods and a constant. There is no code change, no bug fix, and no security-related content.

This commit only updates machine-generated API snapshot text files to add a newly exposed public function, CompactTarget::to_target, to the recorded public interface. There is no source code change, no bug fix, and no security-relevant behavior change in this commit itself.

This commit adds a new convenience method, to_target(), to the CompactTarget type in the rust-bitcoin library. It simply calls the existing Target::from_compact() conversion under the hood and does not change any behavior, security logic, or calculations. It is a routine API ergonomics improvement, not a security fix.

This commit only updates generated text files that list the project's public API surface. The change shows that a Sum trait implementation for a numeric result type was broadened to accept more input types. No actual source code was modified, and there is no indication of a security fix or vulnerability.

This commit only adds new unit tests for summing Amount and SignedAmount values into a NumOpResult. It does not change any production code, fix a bug, or alter behavior. There is no security issue here.

This is a small Rust API ergonomics change. It makes the 'sum' operation more flexible so developers can add up plain Amount values directly into a result type, not just values that are already wrapped in that result type. There is no security-relevant change.

This commit only updates a generated text file that lists the public API surface of the Rust Bitcoin library. It records that several locktime-related types now implement standard serde serialization and deserialization traits. There is no code change, no bug fix, and no security patch in this commit itself.

This commit adds standard data serialization/deserialization support (serde traits) for two relative lock time types in the rust-bitcoin library. It is a routine API completeness change with no security relevance visible in the code or commit message.

This commit adds standard data serialization/deserialization support (serde) for two Bitcoin locktime types: block height and median-time-past. It is an API completeness change, not a security fix or vulnerability. The new code validates values during deserialization using the same existing constructors, so it does not introduce obvious weaknesses.

This commit makes a single internal number field private in a Rust Bitcoin library type called Sequence. It is an API-cleanup change to follow Rust naming conventions (C-STRUCT-PRIVATE). It does not fix a memory corruption bug, a cryptographic flaw, or a consensus issue. Existing code inside the project is updated to use the already-provided public constructor and getter, so behavior is unchanged.

This commit removes the automatic default value for the Bitcoin transaction `Sequence` type in the rust-bitcoin library. Previously, code that asked for a default sequence number would silently get the maximum value (0xffffffff), which disables transaction replacement. The change forces callers to explicitly choose a sequence value, reducing the risk of accidental misconfiguration. It is an API-cleanup change rather than a fix for an active security bug.

This commit fixes a bug in how the Rust Bitcoin library checks the size of individual pieces of data inside a Bitcoin transaction witness. Previously, only the first witness element had its size properly capped; after the first element, the size checker was accidentally reset to a much looser default, allowing oversized elements to slip through. The patch makes sure every single witness element gets the same strict size limit.

This commit fixes an off-by-one bug in how rust-bitcoin checks whether a transaction can yet be spent based on block height. The code was treating a relative locktime of N blocks as satisfied after only N-1 confirmations, instead of the required N confirmations. This could let someone spend coins one block earlier than the Bitcoin protocol allows, which could cause a transaction to be rejected by the network or create inconsistent behavior between this library and other Bitcoin software.

This commit is a cleanup of the project's automated version-compatibility checking scripts. It merges two separate scripts into one and updates the GitHub Actions workflow that runs them. There is no change to the actual Bitcoin library code that users install, so this does not introduce or fix a security vulnerability in the software itself.