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 3fdbd379ed7c29d2a576cc9263582a9933212f90; 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 workflow that bumps the version of a helper tool called cargo-binstall from 1.19.1 to 1.20.0. The tool is only used during automated version-compatibility checks in CI and is not part of the actual rust-bitcoin library that users install. There is no indication this update fixes or introduces a security problem in the project itself.
Recommended action
No security action required. Treat as a normal dependency-maintenance update for CI tooling.
Security signals we found
No strong security signals were identified.
Technical analysis
Evidence from the diff
The commit changes a single pinned GitHub Action reference in .github/workflows/semver-checks.yml from cargo-bins/cargo-binstall@aaa84a43 (v1.19.1) to cargo-bins/cargo-binstall@30b5ca8b (v1.20.0). cargo-binstall is used only in CI to install cargo-semver-checks for running semantic-versioning checks. The upstream release notes mention an IPv6 DNS bugfix, an os-name template variable feature, removal of a Quad9 DNS fallback, and dependency upgrades. None of these are described as security fixes, and the change does not affect the published rust-bitcoin crate or its dependencies.
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…