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 f6c31cbd78e1142d2454ec3fe7979b755c56e12e; successfully ran local tests satsfy: ACK f6c31cbd78e1142d2454ec3fe7979b755c56e12e
✓ 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 commit updates a GitHub Actions automation tool (actions/labeler) used to automatically tag pull requests with labels. It is a routine dependency version bump from 6.2.0 to 7.0.0, with no indication of a security fix or vulnerability. The change only affects internal project workflow automation and does not touch the rust-bitcoin library code that users install.
Recommended action
No security action required. Treat as routine CI/CD maintenance. Review the upstream release notes for any breaking changes to the labeler configuration format before merging, but this is a normal dependency update.
Security signals we found
No strong security signals were identified.
Technical analysis
Evidence from the diff
The commit bumps the pinned GitHub action actions/labeler from commit b8dd2d9 (v6.2.0) to bf12e9b (v7.0.0) in .github/workflows/manage-pr.yml. The upstream v7.0.0 release notes describe the change as a migration to ESM and dependency updates. There is no mention of a security advisory, CVE, or vulnerability fix in the commit message, PR description, or supplied references. The action only labels pull requests and has no access to repository secrets or release artifacts beyond the GITHUB_TOKEN permissions granted to the workflow.
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…