rust-bitcoin

This commit only updates generated text files that list the public API surface of the crate. The change records that a new standard Rust conversion trait (`From<Infallible>`) is now implemented for an existing error type. No source code, logic, or behavior was changed, so there is no security issue here.

This is a routine Rust language addition: it lets the library's network-parsing error type be created from Rust's 'Infallible' type, which can never actually occur. It has no security relevance on its own.

This commit simply rearranges code within a single file. It moves the Display, FromStr, and AsRef implementations for the Network type to appear earlier in the file, and moves the serde-related code lower down. No logic, behavior, or security properties of the code were changed.

This commit simply moves existing code around in the same file. It places the main implementation block for the Network type directly underneath the type definition, which is a common Rust style preference. No behavior, logic, or security properties changed.

This commit only updates three text files that list the project's public API surface. It removes entries for modules, macros, and types that are no longer part of the public API. There is no actual source code change, no bug fix, and no security-related content.

This commit simply deletes two internal helper code modules that were not being used anywhere in the project. It is a cleanup change with no security relevance.

This commit simply deletes unused code—an internal trait and a macro for serde serialization helpers. There is no bug fix, behavior change, or security patch here. It is a routine cleanup that removes dead code.

This commit simply moves an existing helper type used for serializing bytes as hexadecimal from one internal module to another. The code is copied verbatim and made private to the module that uses it. There is no functional change, no bug fix, and no security relevance.

This commit is a simple internal code cleanup. It moves a small helper type used only for formatting debug output from a shared internal utility module directly into the only place it is used, then removes the now-unused utility module. There is no change to how the code behaves or to any security-sensitive logic.

This commit is a routine code cleanup: it moves a small test-only helper macro from a shared internal utility crate into the one place it is actually used. There is no change to user-facing behavior, no bug fix, and no security relevance.

This commit is a pure code reorganization: it moves existing implementations of string formatting, hex display, encoding, and decoding for Bitcoin transactions into a different order within the same file. No logic was changed, no bugs were fixed, and no security behavior was altered.

This commit only moves existing code around in four source files. It reorders the encoding and decoding definitions so they follow the same pattern across the project. No logic was changed, no bugs were fixed, and no security issue is present.

This commit simply stops publicly re-exporting a secp256k1 type called `Verification` from two Rust Bitcoin key modules. It is a routine API cleanup: the type is still available directly from the underlying secp256k1 library, so no cryptographic capability is removed, only a convenience shortcut. There is no security bug or vulnerability here.

This commit only updates project documentation (docs/policy.md). It removes a recommendation to use a third-party 'ordered' crate and instead cautions developers about deriving standard Rust ordering traits on enums because variant order becomes part of the public API. There is no code change and no security fix or vulnerability introduced.

This commit only adds two documentation comments to clarify that hex strings passed to certain Weight constructors are interpreted as weight units. There are no code changes, no behavior changes, and no security implications.

This commit fixes a single-word typo in a documentation comment. The function takes an Amount type, but the comment incorrectly said 'satoshis'. There is no code change and no security impact.

This commit only adds or removes blank lines between constant definitions in four source files to make the code style consistent. It does not change any program logic, values, or behavior, so it has no security relevance.

This commit only changes two documentation comments in the rust-bitcoin library to use a consistent style for writing the number 1000 (with a comma as '1,000'). It does not modify any executable code, logic, or data handling.

This commit only changes the letter case of a variable name in documentation comments, from uppercase 'T' to lowercase 't'. It is a purely cosmetic documentation edit with no effect on code behavior or security.

This commit simply reorders module declarations in a Rust source file so that private modules are listed before public ones. It makes no functional changes to the code and has no security relevance.

This is a one-line documentation-only change in the Rust Bitcoin library. It adds a Rust attribute that prevents a re-exported error type from being shown as inlined in generated API documentation. There is no change to executable code, behavior, or security.

This is a one-word documentation fix in a Rust Bitcoin library comment. It corrects a typo in the user-facing documentation for the FeeRate type, changing 'from_sat_per*' to 'to_sat_per*' so the described function names match the actual API. There is no code change and no security impact.

This commit simply deletes two unit tests that checked deprecated functions still forwarded to their replacements. No production code was changed, so it cannot introduce or fix a security issue on its own.

This commit removes old, deprecated function names and type aliases from the rust-bitcoin `units` crate in preparation for a 1.0.0 release. It is a routine API cleanup: no security bug is fixed and no new unsafe code is added. Downstream projects that still use the removed names will get compile-time errors and must switch to the replacement APIs.

This commit only updates generated text files that list the public API surface of the library. No actual source code, logic, or behavior changed. It is not a security fix and does not introduce or remove any vulnerability.