rust-bitcoin

This commit is a purely stylistic cleanup in the Rust Bitcoin library. It changes how the code tells the compiler which optional features must be enabled for certain pieces of code to compile, switching from combined conditions like `#[cfg(all(feature = "std", feature = "encoding"))]` to stacked single conditions like `#[cfg(feature = "std")]` followed by `#[cfg(feature = "encoding")]`. In Rust, these two forms mean the same thing, so this does not change behavior, fix a bug, or address a security issue.

This commit is a minor Rust code cleanup. It changes one line that previously required both the 'std' and 'alloc' features together into two separate feature checks stacked on top of each other. There is no functional or security change; the compiled result is the same.

This commit is a minor code-style change in the Rust Bitcoin library. It rewrites a single conditional compilation attribute from one combined form into two stacked forms. There is no functional change, no bug fix, and no security relevance.

This commit is a code-style refactor. It replaces single-line Rust conditional annotations like #[cfg(all(A, B))] with stacked separate lines like #[cfg(A)] #[cfg(B)]. The behavior is identical; no security issue is introduced or fixed.

This commit is a routine internal refactoring of the rust-bitcoin project. It moves a helper macro called transparent_newtype from one internal crate to a shared include file, then updates all crates to use the shared version. There is no change to user-facing behavior, no bug fix, and no security relevance.

This commit only fixes the wording and formatting of documentation comments in four source files. It adds backticks around hash function names like `SHA256d` and `SipHash24` so the generated documentation looks consistent. No code behavior changes.

This is a routine GitHub Actions CI maintenance change. It swaps the weekly automated code-formatting job from using a floating nightly Rust toolchain to a custom project tool called cargo-rbmt, which pins the compiler version. There is no user-facing code change and no security-relevant behavior.

This commit is purely a housekeeping change to the project's continuous integration (CI) setup. It moves the files that record the library's public API surface from a shared top-level directory into each individual crate's own directory, and switches the CI workflow to use a different command to check those API files. There is no change to the actual Bitcoin library code that users run, and no security impact.

This is a one-line change to the project's GitHub Actions CI workflow. It adds an explicit git reference (the previous commit SHA) when running pre-release checks, so the check can run correctly after a pull request is merged into the master branch. There is no change to the Rust library code, no security fix, and no vulnerability.

This commit only updates a version identifier for an internal CI/testing tool (rbmt). There are no code changes to the rust-bitcoin library itself, and nothing in the commit suggests any security issue.

This commit is purely a cleanup of developer tooling. It removes old references to a pinned nightly Rust toolchain version from the pre-commit git hook and the justfile (a task runner). The actual toolchain version pins were already moved to the project's main Cargo.toml file in a previous change. There is no change to the library code, no change to how the software behaves for users, and no security relevance.

This commit is a routine code reorganization. It moves the definition of a parsing error type into a new 'error' submodule while keeping the same public name available at the top level. There is no security-relevant change.

This commit is purely a code formatting cleanup. It only reorders an import statement, removes extra blank lines, and reformats an array literal to fit style guidelines. There are no functional changes to the SHA-256 hashing code.

This commit only adds `#[rustfmt::skip]` annotations to three places in a SHA-256 cryptographic implementation file. These annotations tell Rust's automatic code formatter to leave those blocks alone. There is no change to program logic, constants, memory handling, or any behavior that could affect security.

This commit is a pure code reorganization: it moves existing error type definitions from several source files into a new dedicated `error` submodule and re-exports them at the crate root. There are no functional changes to how data is encoded or decoded, no bug fixes, and no security-relevant behavior changes.

This commit only adds documentation examples to two Rust macros. It does not change any executable code, logic, or security behavior. There is no security issue here.

This commit only updates the crate-level documentation in the consensus_encoding module. It expands the list of free-standing encoding and decoding functions with brief descriptions. No code behavior was changed.

This commit removes one blank line from a documentation comment in a Rust source file. It is purely a code-style cleanup with no functional or security relevance.

This commit adds a single blank line in source code between a type declaration and a function declaration for formatting consistency. It does not change any behavior, logic, or security properties of the software.

This commit only reformats documentation comments (rustdoc) in five source files to match the project's preferred 100-column line width. No executable code, logic, or behavior was changed. It is a cosmetic/style-only change with no security relevance.

This commit only fixes grammar in code comments (changing 'Push' to 'Pushes' and 'Complete' to 'Completes'). It does not change any actual program logic, function behavior, or security properties.

This commit simply updates a pinned nightly Rust compiler version in a project file from one weekly snapshot to the next. It is a routine tooling/maintenance change with no visible security relevance.

This commit is a small internal cleanup in the rust-bitcoin library's peer-to-peer message handling. It swaps the raw `u64` numbers used for Bitcoin ping and pong messages with dedicated `Ping` and `Pong` wrapper types. The actual data being sent and received does not change; only the internal code structure is tidied up. There is no security issue here.

This commit is a routine API cleanup in the rust-bitcoin library. It adds new helper methods so that developers can create cryptographic keypairs directly from PrivateKey objects instead of reaching into the underlying secp256k1 secret key. The change does not fix a bug, close a security hole, or alter cryptographic behavior; it only makes the public API more convenient and less error-prone.

This is a routine automated update that changes one line in the project's configuration file, bumping the pinned Rust nightly compiler version from March 13, 2026 to March 27, 2026. There is no code change, no bug fix, and no security-related content.