rust-bitcoin

This commit adds a new `try_push` method to an internal `Buffer` trait used during Base58 encoding. It is a straightforward, additive change that lets encoding code gracefully handle a full fixed-size buffer in no-allocation builds. There is no bug fix, no behavior change to existing code paths, and no security issue visible in the diff.

This commit refactors base58 encoding so the same encoding logic can be reused with a fixed-size, no-allocation buffer (ArrayVec) as well as the existing heap buffer (Vec). It removes several `#[cfg(feature = "alloc")]` guards from shared constants and traits, and introduces a fallible `encode_to_buffer` helper. The change is a code-cleanup/refactoring step toward supporting no-alloc environments; it does not by itself fix a reported security bug.

This commit adds a new type, Base58CkString, for encoding Bitcoin-style base58check strings. It is a routine feature addition that makes encoding work both with and without memory allocation. There is no indication of a security bug or fix.

This commit is a routine internal cleanup in the rust-bitcoin library's base58 module. It removes an unused 'push' method from a private helper trait called Buffer, because the code now uses a fallible 'try_push' method instead. There is no security-relevant change: no behavior is altered, no bug is fixed, and no vulnerability is introduced or removed.

This commit only updates generated API listing files (text snapshots of public functions/types). It adds lines describing two new public methods on script types. There is no source code change, no bug fix, and no security relevance visible in the diff.

This commit is a routine internal code reorganization. It moves two helper methods, `script_hash` and `wscript_hash`, from one Rust module to another within the same project. The methods still do exactly the same thing—compute the same Bitcoin script hashes—and are still called the same way. There is no change to security behavior, no bug fix, and no vulnerability.

This commit adds a simple helper function that returns the default Bitcoin JSON-RPC port number for each supported network (Bitcoin mainnet, Signet, Testnet versions, and Regtest). It is purely additive: it exposes no new network service, changes no existing behavior, and contains no input parsing, cryptography, or memory-unsafe code. There is no security issue here.

This commit only adds blank lines inside documentation comments for three internal helper functions. It changes no executable code, no APIs, and no behavior, so it has no security relevance.

This commit only adds plain-text comments to three copies of the same internal helper function, reminding future developers that the copies should be kept in sync. No code behavior was changed, so it has no security effect on its own.

This commit only removes five documentation comments from the implementation of a Rust trait. The actual code behavior does not change; only the source-code comments are deleted because the documentation is already rendered from the trait definition. There is no security relevance.

This commit only updates two public API listing files (text snapshots of the crate's public interface). It widens which script types can call a helper that builds a Pay-to-Witness-Script-Hash output. There is no code change, no bug fix, and no security behavior change visible in the diff.

This is a small API change in a Bitcoin library written in Rust. It moves a helper function that creates P2WSH (pay-to-witness-script-hash) output scripts so it can be used on more script types. There is no indication this fixes a security bug or introduces a vulnerability; it appears to be a routine feature/cleanup change.

This commit is a pure documentation update. It adds one missing bullet point to the crate-level documentation list, describing a function that already existed. No code behavior changed.

This commit adds one line to the project's .gitignore file so that backup files named Cargo.lock.backup are ignored by Git. It is a routine housekeeping change with no security relevance.

This commit only updates automatically-generated API snapshot text files. The snapshots now show that some error and I/O types are reported as coming from Rust's `core` library instead of the `std` library. This is a documentation/test-artifact change with no functional code modification and no security relevance.

This is a minor code cleanup in the rust-bitcoin library. It moves where a variable is first given a value so that the Rust compiler stops warning about unnecessary late initialization. There is no change to program behavior, no bug fix, and no security relevance.

This is a routine automated update that changes the pinned Rust nightly compiler version in the project's configuration file from one recent nightly to another. There is no code change, no bug fix, and no security-relevant content.

This commit only changes a CI script that lists which Rust crates must follow strict semantic-versioning rules. It adds two already-released 1.0 crates to the hard-fail list so future pull requests will fail automated checks if they accidentally break backward compatibility. There is no change to library code, no bug fix, and no security relevance.

This commit only adds a new Rust package (bitcoin-network-kind) to an existing CI script that checks for accidental breaking changes in public APIs. It does not change any library code, runtime behavior, or security-sensitive logic. There is no security issue here.

This commit only changes a documentation comment for a Rust function. It removes the phrase 'assuming the script is a scriptPubkey' because the code's type system now guarantees the script type. No code behavior was altered, so there is no security impact.

This is a routine patch-version update of a GitHub-maintained security scanning helper (the CodeQL upload-sarif action) inside a CI workflow. It does not change the project's actual Bitcoin library code, its public interfaces, or how user funds or data are handled. There is no indication this commit fixes or introduces a security vulnerability.

This is a routine automated update by Dependabot that changes the version of the GitHub Actions 'checkout' tool used by the project's CI workflows from version 5.0.0 to version 6.0.2. It only affects how the repository code is downloaded during automated testing and release tasks. There is no indication of a security vulnerability being fixed or introduced, and no project source code is changed.

This is a routine update by Dependabot to the GitHub Action used for creating releases. It changes the pinned version of ncipollo/release-action from 1.20.0 to 1.21.0 in the project's release workflow. There is no direct evidence in the commit or supplied references that this update fixes a security vulnerability or introduces one. It is a normal dependency maintenance change.

This is a routine automated update by Dependabot that changes the pinned version of a GitHub Action used to install the 'uv' Python tool in two workflow files. The new version is a major release of the setup-uv action, but the commit itself only updates the pinned commit hash and keeps the same major-version comment. There is no indication in the commit that this fixes a security vulnerability or introduces malicious behavior.

This is a routine automated update by Dependabot that bumps the version of a GitHub Actions caching tool used only in a daily fuzzing workflow. There is no code change to the rust-bitcoin library itself, and nothing in the commit indicates a security problem.