rust-bitcoin

This commit only turns on a Rust style lint (clippy::use_self) and replaces explicit type names with `Self` in the source code. It does not change what the code does, only how it is written. There is no security impact.

This commit is a routine performance and ergonomics improvement. It changes several Rust constructor functions from regular functions to 'const' functions, which lets the compiler precompute some values at compile time rather than runtime. There is no change to security behavior, no bug fix, and no vulnerability patch.

This commit adds public API snapshot files for the consensus_encoding crate and updates a script to include that crate in API change checks. It is purely a tooling and documentation change that records what functions and types are currently exposed to users. There is no change to actual program logic, no bug fix, and no security patch.

This is a routine update to a CI (Continuous Integration) tool version. It changes the version of cargo-public-api used in automated checks from 0.49.0 to 0.50.1, because the older version does not support a Rust language feature called macro_export that the project now uses. There is no security relevance.

This commit only changes three lines of documentation comments for a Cursor type. It updates the description to mention that the position tracking applies to both reading and writing. There is no code change, no behavior change, and no security relevance.

This commit adds a new helper function that lets no-std code write encoded Bitcoin data to custom I/O writers. It is a straightforward feature addition mirroring an existing std-only helper. There is no indication of a security bug, fix, or vulnerability.

This commit adds a normal feature: it lets a Cursor (a wrapper that tracks your position while reading/writing a byte buffer) support writing, not just reading. The implementation matches the standard Rust library pattern and includes unit tests. There is no indication this fixes a bug or addresses a security issue.

This commit is a routine code cleanup that renames some internal conversion functions on the Address type to follow Rust naming conventions. It does not change what the code does, only what the functions are called. The old names are kept as aliases that show a deprecation warning so existing users are not broken.

This commit only updates generated API text files to list three newly exported types (BlockHeightDecoder, BlockHeightDecoderError, BlockHeightEncoder). It contains no code changes, no logic changes, and no security-relevant behavior.

This commit simply makes two existing types (BlockHeightDecoder and BlockHeightDecoderError) publicly visible from a different module. It is a routine API visibility fix with no security relevance.

This commit only updates a generated text file that lists the public API surface of the crate. It renames error types in the listing to match a dependency update (hex_conservative renamed its error types) and adds one newly exported crate. There are no code changes, no behavior changes, and no security fix or vulnerability introduced.

This commit swaps in a newer, stable version of a helper library (hex-conservative 1.0.0) for public-facing parts of the rust-bitcoin 'primitives' crate, while keeping the older version for internal-only uses. It is a dependency/API-stability cleanup, not a fix for a known security bug. There is no direct evidence in the commit that it addresses an exploit or vulnerability.

This commit only changes wording in documentation comments and one inline code comment. It renames 'Secp256k1' to 'secp256k1' and expands the shorthand 'secp' to 'secp256k1' for consistency. No executable code, logic, cryptography, or APIs were modified, so there is no security impact.

This commit simply renames a helper function from encode_to_hash_engine to encode_to_engine and updates the one place that calls it. There is no security change; it is a routine code-style cleanup.

This is a routine dependency update by Dependabot that bumps the GitHub Actions 'upload-artifact' action from version 4 to version 5 in three internal workflow files. There is no code change to the rust-bitcoin library itself, and nothing in the commit suggests a security problem or fix.

This is a routine automated update by Dependabot that bumps a GitHub Actions helper (used to download build artifacts) from version 5 to version 6 in a daily fuzzing workflow. There is no indication of a security vulnerability or malicious change in the commit itself.

This commit simply adds a person's name to the list of authors in a package metadata file. It changes no code, no functionality, and has no security relevance.

This commit adds text files that list the public API of the `bitcoin_primitives` Rust crate and updates a CI script to check that future changes do not alter that API unexpectedly. It is a development tooling and release-preparation change with no effect on runtime behavior or security.

This commit adds a new helper method called is_p2a that lets the library recognize a specific modern Bitcoin address/output type known as P2A (Pay-to-Anchor). It is a pure feature addition with no bug fix, no behavior change to existing code, and no security relevance visible in the commit.

This commit is a routine code-style cleanup. It changes some function return type declarations from explicit type names (like `TxOut` or `CompactTarget`) to `Self` inside Rust extension traits. This has no effect on what the functions do or on security.

This commit only changes developer helper commands in a 'justfile' (a task runner configuration). It removes some convenience recipes for building/checking/formatting the whole workspace and replaces them with crate-specific versions. There is no change to the actual Rust Bitcoin library code, no change to how the software runs for users, and no security relevance.

This commit updates the project's justfile (a task runner configuration) so that commands use absolute paths relative to the justfile's directory. This is a developer-experience and robustness improvement, allowing recipes to be run from subdirectories. There is no security relevance in the changed code.

This commit simply moves a helper command that draws a dependency tree from one project file (the justfile) into its own shell script. It also switches from listing specific crates to excluding only an internal fuzz-testing crate. There is no change to the actual Bitcoin library code, no security fix, and no vulnerability.

This commit removes two shortcut commands from the project's justfile (a task runner configuration). The removed shortcuts were for running tests with the nightly and MSRV Rust toolchains. The commit message says these shortcuts were 'broken' because they did not run with the correct toolchain versions. This is a build/maintenance tooling change, not a code change, and there is no indication of any security issue.

This commit only fixes spelling and grammar in human-readable error messages and a doc comment. It changes 'And I/O error' to 'An I/O error', 'less bits' to 'fewer bits', and 'not all bit were consumed' to 'not all bits were consumed'. There is no code behavior change and no security relevance.