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: tcharding: ACK 054e0d73c502cfdb702ca57d96ea798555ec96a3 apoelstra: ACK 054e0d73c502cfdb702ca57d96ea798555ec96a3; successfully ran local tests
✓ 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 update to a GitHub Actions helper used in automated testing workflows. It changes which version of a third-party tool-installer action is used, but only for installing the cargo-mutants testing tool. There is no indication this affects the actual rust-bitcoin library code, user-facing behavior, or introduces a security vulnerability.
Recommended action
No security action required. This is a standard CI dependency bump. Reviewers may optionally verify the new install-action SHA against upstream release notes.
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.87.4 to 2.87.9 in two workflow files (cron-weekly-cargo-mutants.yml and rust.yml). This action is only used to install cargo-mutants for mutation testing in CI. The diff shows only SHA and version comment changes; no source code, dependencies, or build artifacts consumed by library users are modified. The release notes describe only manifest updates for unrelated tools.
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…