rust-bitcoin

This commit simply renames a GitHub Actions workflow file and changes its schedule from weekly to monthly. It is a routine CI maintenance change with no security relevance.

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 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 is a routine release preparation: it bumps the version number of the `bitcoin-primitives` crate from 0.102.0 to 0.103.0, updates related dependency declarations in other crates, refreshes lock files, and adds a changelog entry. There are no code logic changes and no security fix or vulnerability introduced in the diff itself.

This commit is a routine update to the project's internal continuous-integration tooling. It changes how a helper tool called cargo-rbmt is installed and where its version is recorded, but it does not modify the actual Bitcoin library code or any user-facing behavior. There is no security issue visible in this change.

This commit is a routine version bump for the bitcoin_hashes crate from 1.0.0 to 1.1.0. It updates dependency references across the workspace, records the release in the changelog, and adjusts deprecation lint allowances in tests. There is no security-relevant code change.

This commit is a straightforward API refactor in the BIP-32 (Bitcoin key derivation) code. It replaces a function that returned a raw secret key and chain code with one that returns a new structured type called XpubChildTweak. The actual cryptographic math and behavior remain the same; only the way callers receive the result has changed. There is no indication this fixes a security bug.

This is a routine code cleanup in a Bitcoin library. It renames key-derivation methods on extended public and private keys (Xpub/Xpriv) to clearer names and removes old aliases. There is no security bug being fixed and no new vulnerability introduced; it is purely a refactoring that may require downstream developers to update their code.

This is a routine Dependabot update that bumps a GitHub Actions helper used by automated weekly maintenance workflows to create pull requests. The change only affects internal tooling, not the Rust Bitcoin library code that users rely on. There is no direct evidence of a security vulnerability being fixed or introduced, but any third-party action update carries a small supply-chain risk if the new version were malicious or buggy.

This commit is a routine version bump for the internal 'bitcoin-internals' crate from 0.5.0 to 0.6.0. It updates version numbers across package manifests and lock files, and adds a changelog describing API cleanups and small improvements. There is no code change that fixes a security bug or introduces a vulnerability.

This commit only changes three GitHub Actions workflow files that control scheduled CI jobs. It updates the list of long-term support (LTS) branches used by automated cron jobs, replacing one branch name with two placeholder-looking names ('0.32.xxx' and '0.32.xx'). There are no changes to the Rust Bitcoin library code, no bug fixes, and no security-related modifications.

This commit simply removes an unused software dependency (the hex-conservative crate) from the internals sub-package and updates related package configuration files. It is a routine cleanup change with no security relevance.

This commit only edits the project's README.md file. It removes outdated CI badges, updates the recommended JSON-RPC client library, fixes changelog links, and adds missing crates to the changelog list. No code, build scripts, or cryptographic logic was changed, so it has no direct security impact on users of the library.

This commit is a routine internal code cleanup in the rust-bitcoin project. It swaps old base58 encoding helper functions for a new equivalent type, Base58CkString, in three source files. There is no indication from the commit itself that this fixes a security bug; it appears to be part of a refactoring to remove deprecated functions.

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 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 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 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 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 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 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 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 changes two GitHub workflow files so that an automated bot updates the Rust compiler toolchain on both the master branch and a long-term support branch (0.32.x), instead of only on master. It is a routine CI/CD maintenance change with no security relevance.

This commit adds new ways to print ECDSA Bitcoin signatures as hexadecimal text (lowercase and uppercase), matching formatting already available for Taproot signatures. It also makes the existing Display implementation reuse the new LowerHex implementation. There is no security fix or behavior change that affects signatures themselves—only how they look when formatted as text.