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: satsfy: ACK 42b0bcbbcf0d3d4c4e8394dc3bd4fd804d455598 apoelstra: ACK 42b0bcbbcf0d3d4c4e8394dc3bd4fd804d455598; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ 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 only in automated security-scanning workflows. The new version adds minor improvements, including respecting proxy settings and verifying downloaded files with checksums. It does not fix any reported vulnerability in the rust-bitcoin library itself, nor does it change any code that end users run.
Recommended action
No immediate action required beyond normal CI dependency hygiene. Review the upstream release notes and verify the pinned commit hash matches the official astral-sh/setup-uv release. Continue monitoring Dependabot updates.
Security signals we found
01
Dependency bump of a third-party GitHub Action used in CI only
No CVE, advisory, or vendor security disclosure is present in the commit or supplied references
04
No changes to rust-bitcoin source code, APIs, or cryptographic operations
Technical analysis
Evidence from the diff
The commit bumps the pinned astral-sh/setup-uv action from commit 20cfd1bf945f4377ade1205e4dbc17946fc9a30d to bec219d24cd3e171d82865faccec33120bb574f4 (v10.0.1 to v10.1.0) in two CI workflows: cron-zizmor.yml and zizmor.yml. These workflows run the zizmor static analyzer against the repository. The upstream release notes mention security-hardening items such as checksum verification for downloads, npm install hardening, and NO_PROXY support, but no CVE or advisory is referenced. The change is limited to CI infrastructure and does not affect the published Rust crate or its cryptographic logic.
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…