rust-bitcoin

This commit is a simple housekeeping change for the project's fuzz-testing scripts. It removes a small helper file (fuzz-util.sh) and copies its functions directly into another script (generate-bins.sh). There is no change to the actual Bitcoin library code, no change to how the software handles data, and no security fix or vulnerability introduced.

This commit is a routine cleanup of the project's fuzz-testing shell scripts. It merges the old cycle.sh script into fuzz.sh and adds a -cycle command-line flag. There is no change to the actual Bitcoin library code, no bug fix, and no security patch.

This commit refactors a fuzz-testing shell script to stop using a local helper file and instead use the standard 'cargo-fuzz' tool directly. It is a build/test tooling change with no apparent effect on the security of the actual Bitcoin library code.

This commit changes two GitHub Actions workflow files so that if one branch's automated toolchain update job fails, the other branches' jobs keep running instead of all being cancelled. It is a pure CI reliability/configuration tweak with no product code changes and no security relevance.

This is an automated code-formatting commit from rustfmt. It only changes whitespace, reorders imports, and breaks a long line. There are no functional changes and no security implications.

This commit simply bumps the version number of a third-party CI linting tool (cargo-semver-checks) used in GitHub Actions from 0.48.0 to 0.49.0. It changes one line in a workflow configuration file and has no effect on the actual Bitcoin library code, runtime behavior, or security of the software.

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 simply moves a helper shell script from one folder (contrib/) to another (.github/) and updates the path used by a GitHub Actions workflow. It does not change any project code, cryptographic logic, or how the software behaves for users. There is no security issue here.

This commit adds a new GitHub Actions workflow that automatically adds or removes an 'API diff' label on pull requests after CI finishes. It is a defensive security improvement: it separates the labeling step from the main CI workflow and runs with minimal permissions, following GitHub's own guidance for safely handling pull requests from external branches. There is no indication of a vulnerability being introduced or fixed.

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 is a minor code cleanup that removes an unnecessary copy of the first transaction in a Bitcoin block validation routine. It does not change behavior, fix a bug, or address any security issue.

This is a small Cargo.toml configuration change that forwards feature flags from the taproot-primitives crate to its internal bitcoin-crypto dependency. It does not change any executable code, fix a bug, or alter behavior under current feature usage. The commit is framed as a future-proofing measure, not a security fix.

This commit is a routine cleanup of leftover references to old test scripts in configuration files. It removes stale entries from a GitHub labeler config, .gitignore, and a label generator, deletes an unused helper script, and inlines its only useful content into another script. There is no security-relevant change.

This commit only adds documentation comments to an existing Rust function. It explains what the function returns and how that return value can be reused. No code behavior was changed, so there is no security impact.

This commit is a routine cleanup of the project's internal fuzz-testing scripts. It moves the logic that sets special compiler flags for fuzzing from the GitHub Actions workflow file into the fuzz.sh shell script. There is no change to the actual Bitcoin library code, no change to how user-facing software behaves, and no security fix or vulnerability introduced.

This commit is a routine maintenance change to the project's fuzz-testing build script. It changes how the list of fuzz test programs is generated and written into a configuration file, but it does not alter the actual Bitcoin library code, fix a bug, or change any behavior that end users or network participants would see. There is no security issue here.

This commit simply renames a fuzz-testing helper script from `generate-files.sh` to `generate-bins.sh` and updates the comments and README that reference it. The script's behavior is unchanged. There is no effect on the actual Bitcoin library code or on security.

This commit is a maintenance-only change to the project's automated fuzz testing setup. It switches the daily fuzzing workflow from generating one GitHub Actions job per fuzz target to running targets across a fixed set of 16 shared jobs. It removes the script that generated the workflow file and deletes a verification step that checked every target ran. There is no change to the actual Bitcoin library code, no user-facing behavior change, and no security fix or vulnerability introduced.

This commit fixes an off-by-one error in how the rust-bitcoin library decides whether a Bitcoin transaction's height-based locktime is satisfied. Because the code both added 1 to the current chain tip height and used a 'less than or equal to' comparison, it considered a locktime satisfied one block too early. A transaction that should only be spendable after block 101 could have been treated as spendable once block 100 was the chain tip. The same kind of bug was also present in relative height locktime checks. The fix removes the extra +1 and switches to a strict 'less than' comparison for absolute height locks, and removes the +1 for relative height locks.

This commit is a routine release preparation: it bumps the version number of the `bitcoin-crypto` crate from 0.2.0 to 0.3.0, updates the changelog, and adjusts dependency references in related crates' configuration files and lock files. There are no code changes, bug fixes, or security patches in the diff.

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 commit seals a Rust trait called PushBytesErrorReport so that only two specific internal types can implement it. Sealing prevents outside code from implementing the trait, which reduces the chance that a future change accidentally breaks compatibility or introduces unexpected behavior. It is a defensive hardening change, not a fix for an active security bug.

This commit only adds a new automated test. It does not change any production code. The test checks that building a Witness from a very long iterator (over 4 million empty byte slices) does not accidentally drop elements. It is a regression test following an earlier fix, not a security patch itself.

This commit simply renames a folder from taproot-primitives to taproot_primitives to match Rust naming conventions. It does not change any code behavior, fix a bug, or address a security issue. All references to the folder path in workspace and package configuration files are updated consistently.

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.