Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
ACKs for top commit: apoelstra: ACK 87f8832e8f86941d8c1b8504a901e33b867b1c7a; successfully ran local tests satsfy: ACK 87f8832e8f86941d8c1b8504a901e33b867b1c7a
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
The short version
What changed, and why it matters
This is a routine Dependabot update that changes the version of a third-party GitHub Action (taiki-e/install-action) used in two automated workflow files. The action installs developer tools like cargo-mutants during CI testing. There is no indication in the commit or its description that this fixes a security vulnerability, and the change does not touch the project's actual Bitcoin library code.
Recommended action
No security action required. Treat as normal dependency hygiene for CI infrastructure.
Security signals we found
No strong security signals were identified.
Technical analysis
Evidence from the diff
The commit bumps taiki-e/install-action from 2.86.8 to 2.87.4 in .github/workflows/cron-weekly-cargo-mutants.yml and .github/workflows/rust.yml. Both usages invoke the action with the ‘tool: cargo-mutants’ input. The release notes supplied by Dependabot list only routine version bumps of unrelated tools (uv, protoc, coreutils, zizmor, etc.) and one new tool support entry (kache). No security advisory, CVE, or bug fix relevant to rust-bitcoin is mentioned.
This is a routine code cleanup in a Bitcoin library. It renames a simple data container from KeySource to KeyOrigin and gives it named fields (fingerprint and path) instead of numbered tuple slots (.0 and .1). The serialized format is inte…
This change is a routine internal cleanup: the key_expression crate stops depending directly on the secp256k1 cryptography library and instead uses a re-export provided by another internal crate called crypto. No user-facing behavior, type…
This is a small Cargo.toml fix in a Rust Bitcoin subcrate. When the optional 'serde' feature was enabled on the key_expression crate alone, it did not also enable serde on the network crate. That meant a type called NetworkKind could not b…