rust-bitcoin

This is a purely cosmetic code cleanup. A public re-export statement was moved to sit with other public re-exports and prefixed with `self::`. The commit message explicitly says 'No logic change' and the diff confirms only two lines were reordered with no functional difference.

This commit adds a new automated security scanner called zizmor to the project's GitHub Actions CI pipeline. It only runs when pull requests modify files under the .github/ directory. There is no code change to the library itself and no vulnerability is being fixed or introduced.

This commit only adds code-quality comments to two GitHub workflow files so that the zizmor security linter stops flagging the use of 'pull_request_target' and 'workflow_run' triggers. It does not change any workflow logic, permissions, or behavior, and therefore has no direct security impact on the project itself.

This commit adds a new scheduled GitHub Actions workflow that runs an automated security scanner called zizmor against the repository's CI/CD configuration every day. It does not change any application code, fix a bug, or introduce a vulnerability. It is purely a defensive security monitoring addition.

This commit tightens the security settings on the project's GitHub Actions workflows. Previously, these automated scripts likely ran with broad default permissions that could let a compromised action read or modify code, open pull requests, or access secrets. The change sets the default permission to 'none' and then explicitly grants each workflow only the minimum permissions it actually needs (mostly just reading the repository, with write access only where required). This is a defensive hardening measure rather than a fix for an active attack.

This commit changes the project's GitHub Actions CI workflows so that after checking out the source code, the temporary GitHub authentication token is no longer kept in memory for later steps. This is a defensive hardening change: it reduces the risk that a compromised third-party action or malicious build step could steal the token and modify the repository or release artifacts. It does not fix an active bug in the Bitcoin library code itself.

This commit only changes how often the project's automated dependency bot checks for GitHub Actions updates. It adds a 60-day cooldown to Dependabot. There is no code change, no bug fix, and no security vulnerability being patched.

This commit only changes how GitHub Actions automation is configured. It replaces floating version tags like @v5 with exact commit hashes (plus a comment showing the version). This is a standard hardening practice to prevent a compromised third-party action from silently updating under the same tag. It does not change any of the project's actual Bitcoin/Rust code, so it cannot directly introduce or fix a vulnerability in the library users depend on.

This commit is a routine performance improvement, not a security fix. It adds a new way to get an opcode's name as a static string slice without allocating memory, and uses that new method during JSON/serde serialization. There is no change to behavior, no bug fix, and no security relevance in the code itself.

This commit adds a new CI test script that checks whether all public items from one Rust crate (bitcoin_units) are correctly re-exported in another crate (bitcoin_primitives). It does not change any library code, only adds a build/verification script and a GitHub Actions job. There is no security issue here.

This is an automated code-formatting commit from rustfmt. It only changes whitespace, line breaks, and import ordering. There is no functional change and no security relevance.

This commit only adds two new unit tests for existing XOnlyPublicKey functions. It does not change any production code, fix bugs, or alter behavior. There is no security issue here.

This commit adds a simple accessor method that lets users extract the underlying cryptographic key from a wrapper type. It is a routine API addition with no security relevance visible in the code or commit message.

This commit is a routine code-quality cleanup. It turns on a Rust linter rule (clippy::use_self) that encourages using 'Self' instead of repeating a type's name inside its own implementation blocks, and updates the affected code to satisfy the new rule. There is no functional change, no bug fix, and no security relevance.

This commit adds a code-style lint (a Clippy warning) to the fuzz testing crate. It tells developers to prefer `Self` over repeating the type name in implementations. There is no change to runtime code, no bug fix, and no security relevance.

This change only adds a Clippy lint warning in the benchmark crate's configuration. It tells the Rust linter to warn when code could use `Self` instead of repeating the type name. It does not change any executable code, fix any bug, or affect the library's behavior or security.

This commit is a minor code-style cleanup in the base58 subcrate. It turns on a Clippy lint that encourages using 'Self' instead of the type name when calling functions inside an implementation block, and updates two function calls to match. There is no change to behavior, no bug fix, and no security relevance.

This commit only adds a Clippy lint configuration to warn when code uses a type's full name instead of `Self`. It makes no changes to executable code, APIs, or security behavior. There is no security relevance.

This commit only changes style: it replaces explicit type names like Key or Nonce with the Rust shorthand Self inside the same type's implementation block, and adds a Clippy lint to warn about this style in the future. There is no change to program behavior, no bug fix, and no security relevance.

This commit only turns on a code-style lint (clippy::use_self) and makes two tiny style changes so the code passes the new lint. It does not change behavior, fix a bug, or address any security issue.

This commit is a code-style cleanup in the rust-bitcoin library's units crate. It enables a Clippy lint called use_self and replaces explicit type names (like FeeRate, Weight, LockTime) with the shorthand Self inside impl blocks. These changes do not alter program behavior, fix no bugs, and have no security relevance.

This commit is purely a code-style cleanup. It turns on a Clippy lint that encourages using 'Self' instead of repeating type names inside Rust code, then updates many files in the rust-bitcoin hashes crate to follow that style. There is no functional change, no bug fix, and no security impact.

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 purely cosmetic code cleanup. It enables a Rust linter rule (clippy::use_self) that encourages using 'Self' instead of repeating type names inside implementations. The changes only rename type references and do not alter program behavior, data formats, or security checks.

This commit only turns on a code-style lint (clippy::use_self) and updates a few return types and constructor calls to use the preferred 'Self' shorthand. It does not change behavior, fix a bug, or alter any security-relevant logic.