rust-bitcoin

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 is a simple renaming of internal Rust functions from names ending in '_with' to names ending in '_with_decoder'. It does not change what the code does, only what the functions are called, to avoid confusion with another function that already uses '_with' differently. There is no security issue here.

This commit changes an internal CI script so that only major version-number-breaking API changes are flagged, while minor API changes are ignored. It is a workflow/process tweak with no effect on the actual Bitcoin library code that users run.

This commit only adds documentation comments and a single Clippy lint suppression to fix code-style warnings. It does not change any program logic, data validation, or behavior, so it has no security impact.

This commit is a simple code reorganization. It moves four Bitcoin address-version constants (the numeric prefixes that identify mainnet/testnet and pubkey/script addresses) from the main `bitcoin` crate into a new `addresses` crate, then makes the old `bitcoin` constants point to the new ones so existing code keeps working. The actual numeric values do not change.

This commit is a routine internal code reorganization in the rust-bitcoin library. It moves a helper trait (ScriptPubKeyBufExt) and its functions from one internal module to another, and re-exports it so existing users see no change. There is no indication this fixes a security bug or introduces a vulnerability.

This commit is a straightforward internal code refactor: it copies a small private helper function into a new file so it can be reused locally. There is no security-relevant change to behavior, no new public API, and no fix for a vulnerability.

This commit is a routine code reorganization: it moves the WitnessProgram type and its error handling from the main bitcoin crate into a new bitcoin-addresses sub-crate, then re-exports it so existing users still see the same public API. There is no functional change, no bug fix, and no security relevance visible in the diff.

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 only edits a changelog file, adding hyperlinks to previously merged pull requests and fixing a minor formatting bullet point. It does not change any source code, build scripts, tests, or documentation that affects how the software runs.

This is a routine code-maintenance change: the developers are marking an old helper macro as deprecated and telling users how to write the same code by hand. There is no bug fix, no security patch, and no vulnerability being addressed in the commit itself.

This commit is a routine automated code-formatting run by the rustfmt tool. It only changes whitespace, import order, and line breaks in five files. There are no functional changes, no bug fixes, and no security-related modifications.

This commit only updates three generated API snapshot text files so that the documented type aliases for HkdfSha256 and HkdfSha512 point to HashEngine instead of Hash. These are documentation/snapshot files used to track the public API surface; they contain no executable code changes and no security fix or vulnerability.

This commit fixes two broken type aliases (shortcut names) for HKDF, a cryptographic key-derivation helper, in the rust-bitcoin hashes library. The aliases were pointing at the wrong underlying type after a previous refactor, so any code trying to use them would fail to compile. There is no runtime security vulnerability; it is a compile-time API repair.

This commit is a routine code cleanup in the rust-bitcoin library. It replaces a macro used to define SHA-256 tagged hash identifiers with direct Rust code that does the same thing. The actual hash values and behavior are unchanged; only the internal implementation style is different.

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 is a routine update to the project's automated testing configuration. A tool used to run example tests changed its syntax, so the developer updated one line to keep the same tests running the same way. There is no user-facing change and no security relevance.

This commit is a routine maintenance update for the project's automated API snapshot tests. It does not change any actual library code, behavior, or functionality. The changes only update the expected test output files (snapshots) so they match the format produced by newer versions of the testing tools and the Rust compiler. There is no security impact.

This is a routine update to the project's automated testing configuration. It changes how benchmark tests are run in GitHub Actions to match a new version of an internal helper tool (cargo-rbmt 0.4.0). There is no user-facing change and no security relevance.

This is a routine automated update that changes one line in the project's configuration file, bumping the recommended nightly Rust compiler version from June 12, 2026 to June 26, 2026. There is no code change, no bug fix, and no security relevance visible in the commit.

This is an automated version bump of an internal tooling file (rbmt-version) from one commit hash to another. The diff changes a single line containing a commit identifier. There is no code change to the rust-bitcoin library itself and no indication of a security fix or vulnerability.

This is a small internal code cleanup in the rust-bitcoin library. It replaces a slightly longer two-step hashing pattern with a shorter helper function that does the same thing. The actual cryptographic results and behavior are unchanged.

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 adds two new convenience functions to the rust-bitcoin hashes library. They are purely additive helper functions that wrap existing, safe hashing operations into a one-step call. There is no indication of any security bug, fix, or behavior change.

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.