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 7555780d7be2a8cfe0069068712230b5a23df1b0; 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 only in the project's own security-scanning workflows. The change bumps the pinned version of 'setup-uv' from 10.0.0 to 10.0.1, which fixes a transient network-timeout bug during installation. It does not touch the Rust Bitcoin library code, does not change how user funds or data are handled, and is not described by the project as a security fix.
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 updates the pinned commit hash of the third-party GitHub Action astral-sh/setup-uv in two workflow files (cron-zizmor.yml and zizmor.yml). The new version (10.0.1) only tolerates transient manifest timeouts and updates known checksums for uv 0.12.4. The action is used solely to install the uv Python package manager so the project can run the zizmor static analyzer against its own CI workflows. No Rust source code, dependencies consumed by the library, or release artifacts are affected.
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…