RB
← All projectsRust Bitcoin

rust-bitcoin

Rust library for Bitcoin data structures, serialization, consensus encoding, and scripts.

BitcoinCryptographic librariesNormal
Repository coverage

2570 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

612security candidates555second-pass queue2330AI analyses
153commits · 30 days
280commits · 60 days
977commits · 180 days
2058commits · 365 days
Backfill bands
Aug 5 → Feb 6787 seen32 candidatesComplete
Feb 6 → Jun 6878 seen53 candidatesComplete
Jun 6 → Jul 6211 seen15 candidatesComplete
Jul 6 → Aug 5184 seen2 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
702Strong · 80–100
1135Adequate · 60–79
582Thin · 40–59
151Opaque · 0–39
20security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Andrew Poelstra407139251391
Mitchell Bagot659200654068
Tobin C. Harding42167411063
jrakibi1015096069
satsfy (Renato Britto)652235065
Nick Johnson19621190060
Jamil Lambert, PhD12619117062
Fmt Bot351532045
Trevor Arjeski111111069
Shing Him Ng31731056
Martin Habovstiak31629069
Ismail Daif22622050
Analysis record

Published AI watches

Last scanned 35 minutes ago

Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7220: refactor(bip32)!: replace KeySource with KeyOrigin

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…

6bb507b2by Andrew Poelstra+84−33 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7204: key-expression: Get secp256k1 from the crypto dep

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…

d193efc5by Andrew Poelstra+7−107 files
No security note in commit
Informational 17 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

key_expression: Forward serde feature to network

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…

806f1e1fby bytescape30+1−11 file
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7223: build(deps): bump taiki-e/install-action from 2.87.9 to 2.87.13

This is a routine update to a GitHub Actions helper used in automated testing workflows. It bumps the version of taiki-e/install-action, which downloads and installs Rust developer tools during CI runs. There is no change to the actual Bit…

c8ee144aby Andrew Poelstra+2−22 files
No security note in commit
Informational 20 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7224: build(deps): bump astral-sh/setup-uv from 10.0.1 to 10.1.0

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…

Dependency bump of a third-party GitHub Action used in CI onlyUpstream release notes mention generic security improvements (checksum verification, npm install defaults, NO_PROXY)No CVE, advisory, or vendor security disclosure is present in the commit or supplied references
7bc9d696by Andrew Poelstra+2−22 files
No security note in commit
Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7105: Remove derived serde impls for types in stabilising crates

This commit removes automatic serde (serialization/deserialization) code generation from several Rust Bitcoin library crates and replaces it with hand-written implementations. The stated goal is to reduce dependencies and make the code eas…

Manual serde implementations replace derived ones, increasing the surface area for serialization-format bugsNo validation logic changes are visible in the diffNo mention of security fixes, CVEs, or vulnerability reports in commit message or PR description
9eeb7774by Andrew Poelstra+219−4110 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7205: Manual update to rustc stable (to 1.100.0)

This commit updates the project's automated Rust compiler version from 1.99.1 to 1.100.0 and adjusts a CI cache cleanup script to match a new directory layout used by Cargo 1.100. It is purely an infrastructure/maintenance change to keep a…

44e6f0caby Andrew Poelstra+8−22 files
No security note in commit
Informational 18 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7197: ci: bump rbmt to 0.5.5 and fail API job on private dep leak

This is a build-system improvement, not a code change. It updates a CI helper tool and makes the automated API-checking job fail if a private internal crate accidentally becomes part of the public API. That prevents future leaks of interna…

CI guardrail added to prevent private dependency leaks into stable crate public APIsTool bump enables detection of re-exported private dependenciesNo source-code vulnerability is patched
be14c72eby Andrew Poelstra+7−12 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7185: Refactor/bip32 flatten error constructors

This is a minor internal code cleanup in the Rust Bitcoin library. It changes how two functions (Xpriv::decode and Xpub::decode) build their error messages when an input is the wrong length. The behavior is the same before and after; only …

271f662aby Andrew Poelstra+8−61 file
No security note in commit
Informational 24 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7167: units: remove `Denomination::MicroBitcoin`

This is a routine API cleanup, not a security fix. The change removes one way of naming a Bitcoin unit ('MicroBitcoin' / 'uBTC') and keeps the equivalent 'bits' form. Any code that previously used the old name will fail to compile or fail …

No security signal: public API deprecation and enum variant removalNo memory safety, cryptographic, or consensus code modifiedError message change is informational only
d0602195by Andrew Poelstra+53−403 files
No security note in commit
Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7127: key_expression: Reduce `alloc` gating to minimal types

This commit is a code cleanup and feature-gating refactor for the rust-bitcoin library's key_expression crate. It makes more BIP32 (Bitcoin wallet key derivation) types available when the 'alloc' memory allocator feature is disabled, and s…

Refactor of error types and parsing paths for Xpriv/Xpub base58 decodingSwitch from unbounded base58 decode to fixed-size array decode (78 bytes)Removal of explicit length-check error path in favor of decoder-reported length error
c3d27d5dby Andrew Poelstra+60−823 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7039: primitives: Fix daily Miri cron failures with measured test gating

This change only adds `#[cfg_attr(miri, ignore)]` annotations to a handful of slow unit tests so they are skipped when run under Miri, a Rust interpreter used for detecting undefined behavior. It does not change any production code, consen…

1dc09077by Andrew Poelstra+6−03 files
No security note in commit
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7182: Update local dependencies

This commit only updates version numbers in package configuration files (Cargo.toml) for internal dependencies so that all crates in the project require the same minimum versions of shared libraries. There are no code changes, no bug fixes…

06f41225by Andrew Poelstra+7−75 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7179: build(deps): bump taiki-e/install-action from 2.87.4 to 2.87.9

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 indicatio…

4fda66b5by Andrew Poelstra+2−22 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7180: build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

This commit updates the version of a helper tool called cargo-binstall used in two automated GitHub workflows. The change only affects internal build/CI tooling and does not alter the rust-bitcoin library code that users install or run. Th…

53eae24dby Andrew Poelstra+2−22 files
No security note in commit
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7181: build(deps): bump github/codeql-action/upload-sarif from 4.37.9 to 4.38.0

This is a routine update by Dependabot to the GitHub CodeQL upload-sarif action used in a scheduled security scanning workflow. It changes one pinned commit hash to a newer version of the same action. There is no indication this introduces…

4bb555f0by Andrew Poelstra+1−11 file
No security note in commit
Informational 15 AI analysisMessage 81 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

key_expression: Flatten BIP32 decode error construction

This commit is a minor code cleanup in the Rust Bitcoin library. It changes how an error message is built when decoding BIP32 extended keys, switching from one nested construction style to two chained calls. The actual behavior and returne…

c31c11e0by Adewale Ijalana+8−61 file
No security note in commit
Low 36 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#7168: units: add `visit_units` in optional serde visitors

This commit fixes a bug in how optional Bitcoin amount and fee-rate values are read from JSON when those fields are inside a flattened struct and the value is null. Previously, the code would error out because it did not handle a special s…

Deserialization failure in optional numeric types under serde flattenMissing serde visitor method (visit_unit) causing runtime errorsRegression test added for null handling in flattened structs
47340d2fby Andrew Poelstra+79−03 files
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump github/codeql-action/upload-sarif

This is a routine dependency update by Dependabot, bumping the version of a GitHub-provided action used to upload security scan results. There is no indication of a security vulnerability in the project itself or in this change.

fe755619by dependabot[bot]+1−11 file
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

This is a routine automated update by Dependabot that changes the version of a GitHub Action used to install Rust tools in two CI workflows. There is no indication of a security issue in the commit itself, and no verified security referenc…

2ccb0029by dependabot[bot]+2−22 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidateMerge rust-bitcoin/rust-bitcoin#7220: refactor(bip32)!: replace KeySource with KeyOriginby Andrew Poelstra · 6bb507b2 · Nov 19, 2026 · 3 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7220: refactor(bip32)!: replace KeySource with KeyOrigin

1d564630a788847276c825c76d38631e61570ea8 refactor(bip32)!: replace KeySource with KeyOrigin (Trevor Arjeski)

Pull request description:

- Replace `KeySource` tuple with `KeyOrigin { fingerprint, path }` struct for readability and better alignment with BIP-0380 naming convention (preparing for BIP-0380 implementation).


ACKs for top commit:
tcharding:
ACK 1d564630a788847276c825c76d38631e61570ea8
apoelstra:
ACK 1d564630a788847276c825c76d38631e61570ea8; successfully ran local tests; GLM-5.3 read the BIP and was happy with the language


Tree-SHA512: c04628115a855493c8cbe9a8b1e50cead0af3a87255c9cf2cea085660535c4a515826f914ee0b73fd452012151894946083b82785c0fb2fd824531c8024c005e

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 19/100

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 intentionally kept identical, so existing saved data should still load. There is no security bug being fixed here.

Security candidateMerge rust-bitcoin/rust-bitcoin#7204: key-expression: Get secp256k1 from the crypto depby Andrew Poelstra · d193efc5 · Nov 18, 2026 · 7 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7204: key-expression: Get secp256k1 from the crypto dep

806f1e1f8de143911cc878c6319f16c80006a586 key_expression: Forward serde feature to network (bytescape30)
eeb5b20f516d977de45ae47c6e15642e21123483 key_expression: Drop direct secp256k1 dependency (bytescape30)
4ad585f69792de0bf7c7fb36af7b7964fca90da4 key_expression: Forward serde feature to crypto (bytescape30)

Pull request description:

Nothing about behavior, public types, or error variants changes. Only
the route changes, and one less dependency to manage.

crypto already re-exports secp256k1, so key_expression does not need
its own copy of the dependency. Depending on it in two places only
adds a second version requirement to keep in sync.

Use the re-export in bip32.rs and drop the secp256k1 entries from the
std, alloc, serde and arbitrary features. The matching crypto features
already forward to secp256k1, so the enabled feature set is unchanged.

secp256k1 now routes access through crypto.

Closes #7121


ACKs for top commit:
apoelstra:
ACK 806f1e1f8de143911cc878c6319f16c80006a586; successfully ran local tests
tcharding:
ACK 806f1e1f8de143911cc878c6319f16c80006a586


Tree-SHA512: 4e3e5f90de6619328a1f58dda42b5ee5e4da5940c7f674d1c03e356e6a393533bb787b3973a22bddade17640a6b6212dfb06b5a479a1531383fed3697979f7e5

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 15/100

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, types, or error messages change. It is not a security fix and does not introduce any obvious vulnerability.

Security candidateMerge rust-bitcoin/rust-bitcoin#7105: Remove derived serde impls for types in stabilising cratesby Andrew Poelstra · 9eeb7774 · Nov 16, 2026 · 10 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7105: Remove derived serde impls for types in stabilising crates

98d482b05589eb6a07268da594d751e538c525c9 primitives: Remove serde derives from all types (Mitchell Bagot)
904eedc38427c12ad4339edf7633700f2d0af2b1 units: Remove serde derives from all types (Mitchell Bagot)
16bffa0cb3e31da963b2288a955404f509d22ea5 consensus_encoding: Remove derive feature outside tests (Mitchell Bagot)

Pull request description:

The serde derive feature introduces various additional dependencies to the dependency graph. Since derives are harder to reason about, and slow down the compilation with extra deps, it's better to simply provide explicit serde impls for all types and drop the feature.

Remove serde derive feature from consensus_encoding, units and primitives. Replace all serde derives with explicit impls for all remaining types in units and primitives.

Contributes to #4823


ACKs for top commit:
tcharding:
ACK 98d482b05589eb6a07268da594d751e538c525c9
apoelstra:
ACK 98d482b05589eb6a07268da594d751e538c525c9; successfully ran local tests


Tree-SHA512: 7dc603f26f25b38adcb92062f90c16f87fcf5599555f3d547a1526a85c8621d929dd1563ecd217bee849b41ce821789fdbd188976c9b0e005b5f551ee7fc878b

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
consensus or confidential-proof validationsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This commit removes automatic serde (serialization/deserialization) code generation from several Rust Bitcoin library crates and replaces it with hand-written implementations. The stated goal is to reduce dependencies and make the code easier to reason about. The change is a refactoring/cleanup; it does not fix a known security bug, but any mistake in the new hand-written serde code could subtly change how data is serialized or parsed.

Security candidateMerge rust-bitcoin/rust-bitcoin#7205: Manual update to rustc stable (to 1.100.0)by Andrew Poelstra · 44e6f0ca · Nov 14, 2026 · 2 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7205: Manual update to rustc stable (to 1.100.0)

2f1e93c438ba871805e6a4d509dcb6292e6938d5 ci: prune test cache on cargo 1.100 layout (satsfy (Renato Britto))
62e72d6e076465840093ccbd74a54313eb5e4bbc Automated update to rustc stable-1.100.0 (Update Stable Rustc Bot)

Pull request description:

Supersedes https://github.com/rust-bitcoin/rust-bitcoin/pull/7198.

Cargo 1.100 [uses a new directory layout for intermediate build artifacts](https://github.com/rust-lang/rust/blob/1.100.0/RELEASES.md?plain=1#L108). It writes a new directory every build on `build/<package>/<id>` and no longer has `.fingerprint` or `deps` in the profile directory for our jobs to quickly match. In fact, [`Prune workspace artifacts` step](https://github.com/rust-bitcoin/rust-bitcoin/blob/271f662a6890db459e5ab9088f2b09a3598a43ec/.github/workflows/rust.yml#L47-L72) of the `Test` job matches on `.fingerprint`, which would make it fail prune anything and our cache would be saved with workspace artifacts in it.

Measured locally on a whole workspace test build with 1.100.0, the target directory is 1551 MB unpruned and 491 MB after the new loop (376 MB against 119 MB compressed). The repo is at [6.1 GB of the 10 GB cache limit](https://github.com/rust-bitcoin/rust-bitcoin/actions/caches), so unpruned stable caches would pushing other caches to eviction fasting making our CI performance lower.


ACKs for top commit:
tcharding:
ACK 2f1e93c438ba871805e6a4d509dcb6292e6938d5
apoelstra:
ACK 2f1e93c438ba871805e6a4d509dcb6292e6938d5; successfully ran local tests


Tree-SHA512: 5d10db56c822fa16e9a5e2fcdcad24bc34ddc0534ec8cdedb0cc395541114e820a98d47190852051e9aca77530912c51930b4550f1b3787795161dfa0311d33a

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit updates the project's automated Rust compiler version from 1.99.1 to 1.100.0 and adjusts a CI cache cleanup script to match a new directory layout used by Cargo 1.100. It is purely an infrastructure/maintenance change to keep automated tests and build caches working efficiently. There is no change to the actual Bitcoin library code, no bug fix, and no security-related content.

Security candidateMerge rust-bitcoin/rust-bitcoin#7197: ci: bump rbmt to 0.5.5 and fail API job on private dep leakby Andrew Poelstra · be14c72e · Nov 14, 2026 · 2 filesMessage 91 · StrongInformational 18Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7197: ci: bump rbmt to 0.5.5 and fail API job on private dep leak

40ac950acb35ca14e72f45afc3fd2746ed6f95c9 ci: fail API job on private dependency leak (satsfy (Renato Britto))
892bc18ca783fc084f22eb0dfeafb22e65fd2fd8 ci: bump cargo-rbmt to 0.5.5 (satsfy (Renato Britto))

Pull request description:

Closes #3849.

The issue asks for a CI job that greps the API text files to prove nothing from `internals` is in the public API of a stable crate. `cargo rbmt api` now does that check with no effort on our part, through `private = ["bitcoin_internals"]` in each stable crate, so the grep is not needed.

By bumping to rbmt to 0.5.5, we also catch re-exports (new feature). However, it has various exit codes: exit code 1 is a literal error with rbmt binary, 2 is API diff, and 3 is a private dependency leak. An exit code 2 is an API diff, so it should not fail the job, but 1 and 3 should cause the job to fail, which the rust.yml change does here.


ACKs for top commit:
tcharding:
ACK 40ac950acb35ca14e72f45afc3fd2746ed6f95c9
apoelstra:
ACK 40ac950acb35ca14e72f45afc3fd2746ed6f95c9; successfully ran local tests


Tree-SHA512: 8f28a32f1d3d11a65665cf0fbc0ee6ccd78c8aa9d43e41b436ab6c56a025c6c8783da4f0efa9e22fadb07ddf77d2c3662152c30c6174ef9a1cf7b0e937976371

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlmerge-commit duplicate discount
AI analysis · Informational 18/100

This is a build-system improvement, not a code change. It updates a CI helper tool and makes the automated API-checking job fail if a private internal crate accidentally becomes part of the public API. That prevents future leaks of internal implementation details but does not fix any currently exploitable bug.

Security candidateMerge rust-bitcoin/rust-bitcoin#7185: Refactor/bip32 flatten error constructorsby Andrew Poelstra · 271f662a · Nov 13, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7185: Refactor/bip32 flatten error constructors

c31c11e0635791bfb871c0f7f42035ddc292070c key_expression: Flatten BIP32 decode error construction (Adewale Ijalana)

Pull request description:

This PR is in relation to the error-handling pattern proposed in [#6539](https://github.com/rust-bitcoin/rust-bitcoin/issues/6539.)

Replace nested error construction with chained map_err calls in
Xpriv::decode and Xpub::decode.


ACKs for top commit:
tcharding:
ACK c31c11e0635791bfb871c0f7f42035ddc292070c
apoelstra:
ACK c31c11e0635791bfb871c0f7f42035ddc292070c; successfully ran local tests


Tree-SHA512: ca7860eb90ea7daaf3201512d6e5e09ce508623fbb586484741d972b4c9a63144eb77d036642f712c38137d7db87af5910671b74d50d4f58f982dd7349d97d7b

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This is a minor internal code cleanup in the Rust Bitcoin library. It changes how two functions (Xpriv::decode and Xpub::decode) build their error messages when an input is the wrong length. The behavior is the same before and after; only the style of the code changed. There is no security issue.

Security candidateMerge rust-bitcoin/rust-bitcoin#7167: units: remove `Denomination::MicroBitcoin`by Andrew Poelstra · d0602195 · Nov 13, 2026 · 3 filesMessage 93 · StrongInformational 24Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7167: units: remove `Denomination::MicroBitcoin`

f70e925b7a8ee164f8809f26a45b5dd8301a4bf4 units: remove Denomination::MicroBitcoin (satsfy (Renato Britto))

Pull request description:

Forward note: the goal of this PR is ending [the `MicroBitcoin` discussion](https://github.com/rust-bitcoin/rust-bitcoin/issues/3865#issuecomment-6671175891) with NACKs or ACKs already.

This PR makes `MicroBitcoin` (uBTC) and micro sign forms parse into `Bit`. `Bit` and `MicroBitcoin` are the same 100 sat unit. The issue is these two variants, of equal magnitude, prevent use from using a derived `Ord` in `Denomination` and make `Eq` misleading, as well as be confusing and ugly. This is our chance to fix it, we can always add later after 1.0, but never remove.

Quick history on the subject:
- Not much reason was provided for adding `MicroBitcoin` in [#270](https://github.com/rust-bitcoin/rust-bitcoin/pull/270). Came with no rationale, neither variant is mentioned in the review, and every thread that mentioned that touched this did so tangentially, because it was about something else. The idea of dropping it has been [floated](https://github.com/rust-bitcoin/rust-bitcoin/pull/3934#issuecomment-2605422418) [around](https://github.com/rust-bitcoin/rust-bitcoin/pull/3934#issuecomment-2605438327) [before](https://github.com/rust-bitcoin/rust-bitcoin/pull/3934#issuecomment-2605424530).
- Issue [#729](https://github.com/rust-bitcoin/rust-bitcoin/issues/729) plural and singular forms accepted inconsistently
- Issue [#2820](https://github.com/rust-bitcoin/rust-bitcoin/issues/2820) / PR [#2870](https://github.com/rust-bitcoin/rust-bitcoin/pull/2870) removed MilliSatoshi, Nano and Pico as breaking
- Issue [#3865](https://github.com/rust-bitcoin/rust-bitcoin/issues/3865) should stable crates derive Ord on enums
- PR [#3866](https://github.com/rust-bitcoin/rust-bitcoin/pull/3866) / PR [#3934](https://github.com/rust-bitcoin/rust-bitcoin/pull/3934) derive vs manual Ord, both closed without Ord
- Issue [#3941](https://github.com/rust-bitcoin/rust-bitcoin/issues/3941) / PR [#3943](https://github.com/rust-bitcoin/rust-bitcoin/pull/3943) µBTC spelling in docs and parsing
- Issue [#6353](https://github.com/rust-bitcoin/rust-bitcoin/issues/6353) (still open) Ord blocked by duplicate magnitude

Using GitHub code search, I cannot find any big project using either [`Bit`](https://github.com/search?type=code&q=%2FDenomination%3A%3ABit%5Cb%2F%20language%3ARust%20NOT%20path%3Aamount.rs) or [`MicroBitcoin`](https://github.com/search?type=code&q=%2FDenomination%3A%3AMicroBitcoin%5Cb%2F%20language%3ARust%20NOT%20path%3Aamount.rs) outside rust-bitcoin forks.

Arguments for:
- [BIP 176](https://github.com/bitcoin/bips/blob/master/bip-0176.mediawiki) (Status: Complete) declare that bits is "the standard term for 100 satoshis".
- Bitcoin Core has relabelled µBTC to bits in https://github.com/bitcoin/bitcoin/pull/12035 two weeks after the BIP. Today [`bitcoinunits.cpp`](https://github.com/bitcoin/bitcoin/blob/d0f6d9953a15d7c7111d46dcb76ab2bb18e5dee3/src/qt/bitcoinunits.cpp#L36-L47) has one unit, long name `µBTC (bits)`, short name `bits`.
- Electrum has [`BTC, mBTC, bits, sat`](https://github.com/spesmilo/electrum/blob/master/electrum/util.py#L101-L103), but no µBTC.
- Coinbase shipped a [bits display option](https://www.coinbase.com/blog/its-bits) in 2014.
- Modern wallets dropped the unit altogether. [BlueWallet](https://github.com/BlueWallet/BlueWallet/blob/master/models/bitcoinUnits.ts) and Sparrow offer BTC and sats only. When users ask for it back they ask for bits, [sparrow#777](https://github.com/sparrowwallet/sparrow/issues/777) "to match Bitcoin Core (and most other wallets)", [btcpayserver#250](https://github.com/btcpayserver/btcpayserver/issues/250).
- The [Bitcoin Design Guide](https://bitcoin.design/guide/designing-products/units-and-symbols/) writes it "μBTC (bits)" and names the row `bit`.
- The [Bitcoin wiki](https://en.bitcoin.it/wiki/Units) marks `bit` as the frequent name for the micro-bitcoin.
- No wallet prints `uBTC`, which is what our `MicroBitcoin` displays as.

Arguments against:
- [BIP 177](https://github.com/bitcoin/bips/blob/master/bip-0177.mediawiki#addressing-alternative-approaches) (Status: Draft) refutes BIP 176 as "the Bits Proposal". However, it never direclty mentions µBTC, or develop it as an alternative.
- Blockstream [GDK](https://github.com/Blockstream/gdk/blob/master/docs/source/gdk-json.rst) offers both `"ubtc"` and `"bits"` as separate display units, same duplication we have.

This decision is arbitrary and causes us annoyance. I believe we can just declare that `bits` is the "consensus" name for this unit, no need to carry these 2 around. We can always add MicroBitcoin later, post 1.0. And, given the slowness, by the time these BIP discussions conclude, we may even be launching units 2.0.0+ already, so we can do another breaking change.

By ACKing this, you would be making a pragmatic decision in perfect agreement with the current BIP consensus (which may change later).


ACKs for top commit:
tcharding:
ACK f70e925b7a8ee164f8809f26a45b5dd8301a4bf4
Kixunil:
ACK f70e925b7a8ee164f8809f26a45b5dd8301a4bf4


Tree-SHA512: 46ce47703a80f9316d9402fa3ce696842ca71c653383a369750a218e9f00d4290b99338cec0023a148a9674fc9b34dabbf0215d273ed4f54144d7a8db493a5db

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundaryaccess controlconsensus or confidential-proof validationmerge-commit duplicate discount
AI analysis · Informational 24/100

This is a routine API cleanup, not a security fix. The change removes one way of naming a Bitcoin unit ('MicroBitcoin' / 'uBTC') and keeps the equivalent 'bits' form. Any code that previously used the old name will fail to compile or fail to parse those strings, but there is no vulnerability being fixed and no new attack path being opened.

Security candidateMerge rust-bitcoin/rust-bitcoin#7127: key_expression: Reduce `alloc` gating to minimal typesby Andrew Poelstra · c3d27d5d · Nov 10, 2026 · 3 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7127: key_expression: Reduce `alloc` gating to minimal types

9b23b16241fc6ddaca5c55f2a85e9b2f160993f6 Remove unused errors and variants (Mitchell Bagot)
b48052c31731e6ce21dd9e5ae7bfbddd4de83bbd Ungate FromStr and Display for Xpriv and Xpub (Mitchell Bagot)
1f13455f1fd6cba340ea3cbfcee49ad5a6410de0 Gate individual items in bip32 instead of whole module (Mitchell Bagot)
df894f30da75b858fb0925de02e5dc2e51b4c05e Add optional feature gate to impl_array_newtype macro (Mitchell Bagot)

Pull request description:

The key_expression crate currently gates all functionality on alloc. However, most of the bip32 module does not depend on alloc, outside of a few types. Instead of gating the entire module on alloc, only the inner types and functionality that truly depend on alloc should be gated. With the new base58 functionality, this can be achieved with minimal changes.

Adjust gating to only gate minimal types and functionality on alloc.
Adjust FromStr+Display on X key types to use no-alloc base58.
Adjust ParseXp*Error types to support no-alloc base58 errors.


ACKs for top commit:
tcharding:
ACK 9b23b16241fc6ddaca5c55f2a85e9b2f160993f6
apoelstra:
ACK 9b23b16241fc6ddaca5c55f2a85e9b2f160993f6; successfully ran local tests


Tree-SHA512: 1df13fcc0af1412ffe8e077cb76cb47a3f797b70837ffdfb52f3ede963c1910a78c672139cb6b8901f8f767ce3ddcb3ad2e49996734af369f0da796ef2b6eca6

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This commit is a code cleanup and feature-gating refactor for the rust-bitcoin library's key_expression crate. It makes more BIP32 (Bitcoin wallet key derivation) types available when the 'alloc' memory allocator feature is disabled, and switches Xpriv/Xpub string parsing to use a no-alloc base58 decoder. There is no direct security vulnerability visible in the diff; it is primarily a maintainability and no-alloc compatibility improvement.

Security candidateMerge rust-bitcoin/rust-bitcoin#7180: build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0by Andrew Poelstra · 53eae24d · Nov 9, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7180: build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0

2ccb002995982586511810e1d726e23b8017e361 build(deps): bump cargo-bins/cargo-binstall from 1.22.0 to 1.23.0 (dependabot[bot])

Pull request description:

Bumps [cargo-bins/cargo-binstall](https://github.com/cargo-bins/cargo-binstall) from 1.22.0 to 1.23.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/cargo-bins/cargo-binstall/releases">cargo-bins/cargo-binstall's releases</a>.</em></p>
<blockquote>
<h2>v1.23.0</h2>
<p><em>Binstall is a tool to fetch and install Rust-based executables as binaries. It aims to be a drop-in replacement for <code>cargo install</code> in most cases. Install it today with <code>cargo install cargo-binstall</code>, from the binaries below, or if you already have it, upgrade with <code>cargo binstall cargo-binstall</code>.</em></p>
<h4>In this release:</h4>
<ul>
<li>prefix human-readable logs with cargo-binstall (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2575">#2575</a> <a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2645">#2645</a>)</li>
</ul>
<h4>Other changes:</h4>
<ul>
<li>Upgrade dependencies</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/b874e25ea559687bec77e281e9b271aa1367b624"><code>b874e25</code></a> release: cargo-binstall v1.23.0 (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2655">#2655</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/92a3953f1755f3d00440b0114b709417f02325a0"><code>92a3953</code></a> chore: release (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2648">#2648</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/5baa19648a0d200b36a812f563a83ebfd2e06820"><code>5baa196</code></a> fix: prefix human-readable logs with cargo-binstall (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2645">#2645</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/bbdafe4f550ab376e1ef06325461f613d9a24851"><code>bbdafe4</code></a> build(deps): bump astral-tokio-tar from 0.6.4 to 0.7.0 in the deps group (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2654">#2654</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/9ef12faecb70a6811561bc924b14c09230a9b77e"><code>9ef12fa</code></a> dep: Upgrade transitive dependencies (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2653">#2653</a>)</li>
<li><a href="https://github.com/cargo-bins/cargo-binstall/commit/5aafaaca52423a22d83a812fa3ca77492e2895db"><code>5aafaac</code></a> dep: Upgrade transitive dependencies (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2647">#2647</a>)</li>
<li>See full diff in <a href="https://github.com/cargo-bins/cargo-binstall/compare/75b4bfae1b2c753a6806bbce6e6cb89b602de33c...b874e25ea559687bec77e281e9b271aa1367b624">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cargo-bins/cargo-binstall&package-manager=github_actions&previous-version=1.22.0&new-version=1.23.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<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 2ccb002995982586511810e1d726e23b8017e361
apoelstra:
ACK 2ccb002995982586511810e1d726e23b8017e361; successfully ran local tests


Tree-SHA512: ed7a238f71936e1bd306cc090a15d3e00803f76e6dfdfb5ea913e347364c0828097efe2941218ffc1929220fa11415d09c5cac5b030a4fdd70a2536699abd62e

96/100 · StrongMessage clarity
✓ 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
Why it was queued
access controldocumentation-only discountautomated dependency-update discountmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit updates the version of a helper tool called cargo-binstall used in two automated GitHub workflows. The change only affects internal build/CI tooling and does not alter the rust-bitcoin library code that users install or run. There is no indication this update fixes a security issue or introduces a vulnerability.

Security candidateMerge rust-bitcoin/rust-bitcoin#7181: build(deps): bump github/codeql-action/upload-sarif from 4.37.9 to 4.38.0by Andrew Poelstra · 4bb555f0 · Nov 9, 2026 · 1 fileMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7181: build(deps): bump github/codeql-action/upload-sarif from 4.37.9 to 4.38.0

fe755619b3416a1a6d26677ec52d95fcd2959aa7 build(deps): bump github/codeql-action/upload-sarif (dependabot[bot])

Pull request description:

Bumps [github/codeql-action/upload-sarif](https://github.com/github/codeql-action) from 4.37.9 to 4.38.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/github/codeql-action/releases">github/codeql-action/upload-sarif's releases</a>.</em></p>
<blockquote>
<h2>v4.38.0</h2>
<ul>
<li>On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. <a href="https://redirect.github.com/github/codeql-action/pull/4124">#4124</a></li>
<li>The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native <code>linux-arm64</code> CodeQL bundle when available. <a href="https://redirect.github.com/github/codeql-action/pull/4072">#4072</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.0">2.27.0</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4129">#4129</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action/upload-sarif's changelog</a>.</em></p>
<blockquote>
<h1>CodeQL Action Changelog</h1>
<p>See the <a href="https://github.com/github/codeql-action/releases">releases page</a> for the relevant changes to the CodeQL CLI and language packs.</p>
<h2>[UNRELEASED]</h2>
<p>No user facing changes.</p>
<h2>4.39.3 - 04 Nov 2026</h2>
<ul>
<li>Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. <a href="https://redirect.github.com/github/codeql-action/pull/4283">#4283</a></li>
</ul>
<h2>4.39.2 - 03 Nov 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.4">2.27.4</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4284">#4284</a></li>
<li><em>Upcoming breaking change</em>: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. <a href="https://redirect.github.com/github/codeql-action/pull/4266">#4266</a></li>
<li>Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See <a href="https://github.blog/changelog/2026-10-19-codeql-changes-for-macos-27-xcode-27-and-swift-6-4/">this blog post for more information</a>. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the <a href="https://docs.github.com/en/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/use-the-tools-status-page-for-code-scanning">Tool Status Page</a>. This check will be rolled out following this release of the CodeQL Action. <a href="https://redirect.github.com/github/codeql-action/pull/4221">#4221</a></li>
<li>The undocumented TRAP cache cleanup feature that could be enabled using the <code>CODEQL_ACTION_CLEANUP_TRAP_CACHES</code> environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The <code>analyze</code> Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the <code>trap-caching: false</code> input to the <code>init</code> Action. <a href="https://redirect.github.com/github/codeql-action/pull/4243">#4243</a></li>
</ul>
<h2>4.39.1 - 21 Oct 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.3">2.27.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4256">#4256</a></li>
</ul>
<h2>4.39.0 - 15 Oct 2026</h2>
<ul>
<li><em>Breaking change</em>: Bump the minimum required CodeQL bundle version to 2.20.7. <a href="https://redirect.github.com/github/codeql-action/pull/4205">#4205</a></li>
<li>The <code>codeql-action/analyze</code> step now validates that a correct argument for the <code>checkout_path</code> input has been provided. The <code>checkout_path</code> input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by <code>codeql-action/init</code>, then the CodeQL Action now produces a warning. <a href="https://redirect.github.com/github/codeql-action/pull/4148">#4148</a></li>
<li>Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. <a href="https://redirect.github.com/github/codeql-action/pull/4206">#4206</a></li>
<li>The <code>codeql-action/start-proxy</code> step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as <code>codeql-action/init</code>. This primarily benefits customers who are using GitHub instances other than <code>github.com</code> where the <code>codeql-action/start-proxy</code> step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. <a href="https://redirect.github.com/github/codeql-action/pull/4198">#4198</a></li>
</ul>
<h2>4.38.3 - 08 Oct 2026</h2>
<ul>
<li><em>Upcoming breaking change</em>: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. <a href="https://redirect.github.com/github/codeql-action/pull/4188">#4188</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.2">2.27.2</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4203">#4203</a></li>
<li>Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/4184">#4184</a></li>
</ul>
<h2>4.38.2 - 24 Sept 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.1">2.27.1</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4160">#4160</a></li>
</ul>
<h2>4.38.1 - 18 Sept 2026</h2>
<ul>
<li>The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. <a href="https://redirect.github.com/github/codeql-action/pull/4146">#4146</a></li>
</ul>
<h2>4.38.0 - 09 Sept 2026</h2>
<ul>
<li>On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. <a href="https://redirect.github.com/github/codeql-action/pull/4124">#4124</a></li>
<li>The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native <code>linux-arm64</code> CodeQL bundle when available. <a href="https://redirect.github.com/github/codeql-action/pull/4072">#4072</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.27.0">2.27.0</a>. <a href="https://redirect.github.com/github/codeql-action/pull/4129">#4129</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/github/codeql-action/commit/b96794f015dfd88f77b49b1c93e0fa7110f94c63"><code>b96794f</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4131">#4131</a> from github/update-v4.38.0-7e08580a9</li>
<li><a href="https://github.com/github/codeql-action/commit/02d5093871674ea20274117103ce3038c73c77ef"><code>02d5093</code></a> Update changelog for v4.38.0</li>
<li><a href="https://github.com/github/codeql-action/commit/7e08580a93dc4e4b9dda167e364577035cf504c6"><code>7e08580</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4130">#4130</a> from github/henrymercer/workflow-runner-sizing</li>
<li><a href="https://github.com/github/codeql-action/commit/bfcc52b4f5d98468a5993daa0bf0e4fb3f3ed698"><code>bfcc52b</code></a> Run slow macOS checks on larger runners</li>
<li><a href="https://github.com/github/codeql-action/commit/8c251e757c0260283fc50214a06ac768b61d3af4"><code>8c251e7</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4129">#4129</a> from github/update-bundle/codeql-bundle-v2.27.0</li>
<li><a href="https://github.com/github/codeql-action/commit/0b7ca400df35985869d4b9146a067865d4115da1"><code>0b7ca40</code></a> Add changelog note</li>
<li><a href="https://github.com/github/codeql-action/commit/40484b339517c6bcf00f81eebc95ca041ddca505"><code>40484b3</code></a> Update default bundle to codeql-bundle-v2.27.0</li>
<li><a href="https://github.com/github/codeql-action/commit/977e6ceaea7361825998245d787fa3b4d6b9e5df"><code>977e6ce</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/4124">#4124</a> from github/henrymercer/toolcache-bundle-cleanup</li>
<li><a href="https://github.com/github/codeql-action/commit/40a6b3824794ae1156e1a5320d32e364bf1dcebc"><code>40a6b38</code></a> Address toolcache cleanup review feedback</li>
<li><a href="https://github.com/github/codeql-action/commit/deece8f852f048bc3f52fd42c9cc7a99b1ebb252"><code>deece8f</code></a> Apply suggestion from <a href="https://github.com/henrymercer"><code>@​henrymercer</code></a></li>
<li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/cdf488f595d80d6e07e03d4674febd5ab45fa938...b96794f015dfd88f77b49b1c93e0fa7110f94c63">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github/codeql-action/upload-sarif&package-manager=github_actions&previous-version=4.37.9&new-version=4.38.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<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 fe755619b3416a1a6d26677ec52d95fcd2959aa7
apoelstra:
ACK fe755619b3416a1a6d26677ec52d95fcd2959aa7; successfully ran local tests


Tree-SHA512: ed0741d0197f6a000929d349fe407e97bfbfcb3bdcdeae7d2d2578c7206ef389eb0f3e145afe6e7f75d569acce5c59773acb46f4dd51713b67839f142ff34a5f

96/100 · StrongMessage clarity
✓ 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
Why it was queued
access controldefensive validationdocumentation-only discountautomated dependency-update discountmerge-commit duplicate discount
AI analysis · Informational 15/100

This is a routine update by Dependabot to the GitHub CodeQL upload-sarif action used in a scheduled security scanning workflow. It changes one pinned commit hash to a newer version of the same action. There is no indication this introduces a vulnerability or fixes one; it is normal dependency maintenance.

Security candidatekey_expression: Flatten BIP32 decode error constructionby Adewale Ijalana · c31c11e0 · Nov 9, 2026 · 1 fileMessage 81 · StrongInformational 15Details
Commit message · Adewale Ijalana

key_expression: Flatten BIP32 decode error construction

Replace nested error construction with chained map_err calls in
Xpriv::decode and Xpub::decode.

This separates XkeyDecodeError construction from its wrapping in
XprivDecodeError and XpubDecodeError, improving readability and
following the error-handling pattern proposed in #6539.

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Informational 15/100

This commit is a minor code cleanup in the Rust Bitcoin library. It changes how an error message is built when decoding BIP32 extended keys, switching from one nested construction style to two chained calls. The actual behavior and returned error values remain the same. There is no security fix or vulnerability here.

Security candidateMerge rust-bitcoin/rust-bitcoin#7125: refactor(bip32)!: make xkey fields private and add checked partsby Andrew Poelstra · c532ab9c · Nov 8, 2026 · 5 filesMessage 91 · StrongLow 37Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7125: refactor(bip32)!: make xkey fields private and add checked parts

87512bb4790f13618fd68ebb84696c89ef621574 refactor(bip32)!: make extended-key fields private (Trevor Arjeski)
de4857e2c942ee2a747ae2e43eebb5606079c244 feat(bip32): add checked extended-key parts APIs (Trevor Arjeski)
0a180f7a662b98f05f9486297ad767ace9a3e60a fix(bip32): make Xpriv debug redaction consistent (Trevor Arjeski)

Pull request description:

Continuation of my (slow) refactor of the bip32 module.

- Add public-field `XprivParts` and `XpubParts`, checked `from_parts`,
and `to_parts`.
- Add metadata getters and make `Xpriv`/`Xpub` fields private.
- Share master-metadata validation through `InvalidXkeyPartsError`.
- Use fixed private-key redaction in `Xpriv` and `XprivParts` debug
output, with and without `std`. Metadata remains visible. This was
fixed years ago in `secp256k1`.
- Re-export `secp256k1` for consumers constructing parts.
- Migrate the BIP32 example and update API documentation and changelogs.


ACKs for top commit:
apoelstra:
ACK 87512bb4790f13618fd68ebb84696c89ef621574; successfully ran local tests; yeah, I think this is a reasonable API


Tree-SHA512: e15554a84daa2c48edd5caf6404858670737266ed3e9a0efb6e7d43d686d51a76d4dc3e346be2ed10987c606755e0fb6976e4ed62f501dd97986616ed7b2594a

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Low 37/100

This commit is a routine API refactor, not a security fix. It makes the internal fields of Bitcoin extended keys (Xpriv/Xpub) private so callers can no longer directly mutate them, adds checked constructors that validate master-key metadata, and ensures debug logs always hide the private key. These are defensive hardening changes that reduce the chance of future misuse, but they do not patch an active vulnerability.

Security candidateMerge rust-bitcoin/rust-bitcoin#7128: units: use checked subtraction/addition assignment for NumOpResultby Andrew Poelstra · defb97db · Nov 6, 2026 · 3 filesMessage 100 · StrongModerate 62Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7128: units: use checked subtraction/addition assignment for NumOpResult

201eca08c7f57d0e24ea54336476ec6857473a8b units: use impl_checked_assign! macro for amount and SignedAmount (jrakibi)
2013eb88f6bb5a0fd15846801398b72d7ff2ac82 units: test NumOpResult += and -= overflow (jrakibi)
054045b4d1daf52656e54b32de780ad975696828 units: use checked addition assignment for NumOpResult (jrakibi)
76036ac493b69812f4908ca69bc435e5305b83f3 units: use checked subtraction assignment for NumOpResult (jrakibi)

Pull request description:

`NumOpResult` is supposed to prevent overflow, as mentioned in the docs.

However, addition and subtraction assignment (`+=` and `-=`) currently use the wrapped type regular subtraction/addition instead of **_checked_** subtraction/addition. This can silenly wrap in release builds whilekeeping the result `Valid`.

This change adds checked addition and subtraction for `FeeRate`, `Weight`, `u64`, and `i64`.
`Amount` and `SignedAmount` already handle overflow correctly, so we only change the implementation for these four types.

This is a breaking change since we replace the generic impl with implementations for the four types mentioned above.

Found while auditing `units` crate with Codex.


ACKs for top commit:
Kixunil:
ACK 201eca08c7f57d0e24ea54336476ec6857473a8b
tcharding:
ACK 201eca08c7f57d0e24ea54336476ec6857473a8b
apoelstra:
ACK 201eca08c7f57d0e24ea54336476ec6857473a8b; successfully ran local tests


Tree-SHA512: e221721d0a0c44814aa2321d19f6b62e92d7d98bb11a4ac4b3d90b6e2bd45d761d4075e207c556e861e158974122f2e6199a4b637c08843c039fc5b765c822b5

100/100 · StrongMessage clarity
✓ 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
Why it was queued
memory safetymerge-commit duplicate discount
AI analysis · Moderate 62/100

This commit fixes a bug in the rust-bitcoin library's 'units' crate where the += and -= operators on a special result type (NumOpResult) could silently wrap around on overflow in release builds, instead of reporting an error as documented. The patch replaces the wrapping behavior with checked arithmetic for several numeric types including fee rates, weights, block intervals, and raw integers. It is a defensive fix that prevents incorrect values from being treated as valid.

Security candidateunits: remove Denomination::MicroBitcoinby satsfy (Renato Britto) · f70e925b · Nov 5, 2026 · 3 filesMessage 58 · ThinInformational 21Details
Commit message · satsfy (Renato Britto)

units: remove Denomination::MicroBitcoin

uBTC and micro sign forms no longer parse. Bit and
MicroBitcoin are the same 100 sat unit. Two variants of
equal magnitude block a derived Ord and make Eq misleading.

Bits is the name in use by other projects and docs. For
example, BIP 176 names it the standard term for 100 sat,
Core relabelled micro BTC to bits in 2017 and Electrum
offers BTC, mBTC, bits, sat. No wallet prints uBTC. So bits
is the "consensus" name for the unit.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
consensus or confidential-proof validation
AI analysis · Informational 21/100

This commit removes support for the old 'microbitcoin' unit (uBTC/µBTC) from the Rust Bitcoin library and tells users to use 'bits' instead, since both mean the same 100-satoshi unit. It is a deliberate API cleanup, not a security fix. The change could break applications that still parse or display uBTC strings, but it does not create a vulnerability.

Security candidateunits: rename TooBigForRelativeHeightErrorby satsfy (Renato Britto) · dab7872c · Nov 5, 2026 · 5 filesMessage 58 · ThinInformational 20Details
Commit message · satsfy (Renato Britto)

units: rename TooBigForRelativeHeightError

Relative locktime wording moved from height to block count
(NumberOfBlocks), and this error still used the defunct height.
BlockCountOverflowError matches its sibling TimeOverflowError.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
memory safety
AI analysis · Informational 20/100

This commit is a simple renaming of an error type from TooBigForRelativeHeightError to BlockCountOverflowError to match updated terminology in the codebase. It does not change any behavior, logic, or security properties. It only updates public re-exports and test references to use the new name.

Security candidateMerge rust-bitcoin/rust-bitcoin#7103: Release tracking PR: ` crypto 0.4.0`by Andrew Poelstra · f0fdd87e · Nov 4, 2026 · 13 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7103: Release tracking PR: ` crypto 0.4.0`

56084202392abdffb4c6cb847bd0d80c11918e28 crypto: Bump version to 0.4.0 (Tobin C. Harding)
09cac23981e5acccf951f41e63cabc91c9f50d45 crypto: Update hashes dependency version (Tobin C. Harding)

Pull request description:

In preparation for release add a changelog entry, bump the version number, and update the lock files.


ACKs for top commit:
apoelstra:
ACK 56084202392abdffb4c6cb847bd0d80c11918e28; successfully ran local tests


Tree-SHA512: 51465f4e7921bbe07842c045c97ea2d6cffa09b79abda267229ebc7c6fe43dc2330cd378118c67e9a9bae0fcbc94f1b99d01a199d1414bcb768a4b7e38e61269

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This is a routine release-preparation commit for the bitcoin-crypto 0.4.0 crate. It bumps version numbers, updates dependency version pins, refreshes lock files, fills in the release date in the changelog, and replaces placeholder deprecation strings with the actual release version. There are no code behavior changes and no security fixes or security-relevant claims in the commit message or diff.

Security candidateMerge rust-bitcoin/rust-bitcoin#7150: crypto: drop error prefix, remove deprecated fnby Andrew Poelstra · 732c2692 · Nov 4, 2026 · 1 fileMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7150: crypto: drop error prefix, remove deprecated fn

d34f8f783f82f337aefc6678a244b2fc484c4b39 crypto: drop Invalid prefix from FromSliceError variants (satsfy (Renato Britto))
110d3e92517f0df80c70ce088454536d0c7cacfc crypto: remove deprecated TweakedKeypair::to_inner (satsfy (Renato Britto))

Pull request description:

Split out of https://github.com/rust-bitcoin/rust-bitcoin/pull/7140.

- Remove useless profix `Invalid` from `FromSliceError` variants.
- `TweakedKeypair::to_inner` is deprecated for `into_keypair` since 0.32.6.

Both of these trip clippy once the exported API is linted.


ACKs for top commit:
tcharding:
ACK d34f8f783f82f337aefc6678a244b2fc484c4b39
apoelstra:
ACK d34f8f783f82f337aefc6678a244b2fc484c4b39; successfully ran local tests


Tree-SHA512: 7dc9e7d2b3d7a70202644b1640da71ae9c47d3d890949b6ed97ab177b1e86dde19801c92ccd2a1e28623c4e7116541cf58b010f21513353b938d2c3647047756

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This is a routine code cleanup merge. It renames error variants to remove the word 'Invalid' (for example 'InvalidLength' becomes 'Length') and removes a deprecated function that users were already told to stop using. There is no security fix or vulnerability here.

Security candidateMerge rust-bitcoin/rust-bitcoin#6717: Release tracking PR: `primitives 0.104.0`by Andrew Poelstra · 4432f7c4 · Nov 2, 2026 · 11 filesMessage 100 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#6717: Release tracking PR: `primitives 0.104.0`

8b07e38a1e23ceca780cb71ece6ca99f9ea003f0 primitives: Bump version to 0.104.0 (Tobin C. Harding)

Pull request description:

In preparation for release add a changelog, bump the version, update the lock files, and upgrade all crates to use the new version.

This is a release of what we have so that we can consider doing a `rust-bitcoin` release in series with the final push towards the last RC of primitives.


ACKs for top commit:
apoelstra:
ACK 8b07e38a1e23ceca780cb71ece6ca99f9ea003f0; successfully ran local tests


Tree-SHA512: eb171ff58e2982df1a37dc5aee0dade6d875b25a5b4e9845bd5efc206d904627992c99a6ab1be6e666c3bca621175db01fc8c4c6f626540e16460f5b5340c9d3

100/100 · StrongMessage clarity
✓ 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
Why it was queued
cryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This is a routine release-management commit. It bumps the version of the `bitcoin-primitives` crate from 0.103.x to 0.104.0, updates dependency version numbers in other crates, refreshes lock files, and adds a changelog. There are no code logic changes in the diff itself.

Security candidateMerge rust-bitcoin/rust-bitcoin#7126: Add `Vec` support to `XOnlyPublicKey` serde implsby Andrew Poelstra · 26728d51 · Oct 31, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7126: Add `Vec` support to `XOnlyPublicKey` serde impls

9b32af1e087e4b15b887354aadf60af365bb7668 Add vec support to XOnlyPublicKey serde impls (Mitchell Bagot)

Pull request description:

The recent XOnlyPublicKey serde modules have support for Option, but not for Vec. Since vectors are a standard thing to implement serde traits for, support for them should also be provided in the x_only_serde module.

Add vec submodules to support Vec<XOnlyPublicKey> in x_only_serde.

Contributes to #5787

Assisted by: Claude Opus 5.5


ACKs for top commit:
apoelstra:
ACK 9b32af1e087e4b15b887354aadf60af365bb7668; successfully ran local tests
tcharding:
ACK 9b32af1e087e4b15b887354aadf60af365bb7668


Tree-SHA512: a2d4eb6741ac40d6950e81bd268c0060981aae4c4cdd9273d93e33598a77c7d1465e63aaa90e96c36937367be128595d5bdc2f05b6bb8b16300d45ef191c6dfb

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit adds new helper code for serializing and deserializing lists of Bitcoin x-only public keys using the serde framework. It is a feature addition, not a bug fix, and there is no indication it addresses a security vulnerability.

Security candidateMerge rust-bitcoin/rust-bitcoin#7097: units: Match rustdoc heading of other 1.0 cratesby Andrew Poelstra · f015e2db · Oct 31, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7097: units: Match rustdoc heading of other 1.0 crates

6ea685ddeba97febf9f747c55fb594f49d2599c6 units: Match rustdoc heading of other 1.0 crates (Tobin C. Harding)

Pull request description:

Change the crate level header to match the format of `primitives` and `consensus_encoding`. Also use the first sentence from primitives docs but with `s/primitive/units`.

FWIW the heading comes from e86502cc49

Close: #7089


ACKs for top commit:
satsfy:
ACK 6ea685ddeba97febf9f747c55fb594f49d2599c6
apoelstra:
ACK 6ea685ddeba97febf9f747c55fb594f49d2599c6; successfully ran local tests


Tree-SHA512: b8f5e542d14fe3f11cd156e53978d79ae25f44727b79814e3a9b676fd9b11be51428c4529a80a7892be88a5343a0e975a8a383372ecaf63421f7ea5b09f14244

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
consensus or confidential-proof validationmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit is a documentation-only change. It updates the heading and first sentence of the crate-level documentation in the `units` crate to match the style used by other crates in the project. No code behavior was changed.

Security candidateMerge rust-bitcoin/rust-bitcoin#7139: ops: harden ci workflowsby Andrew Poelstra · fb0c6a07 · Oct 31, 2026 · 3 filesMessage 91 · StrongLow 37Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7139: ops: harden ci workflows

0c6f37729b8f003a3af10e9f8c0ed00a12876200 ops: harden ci workflows (Felipe Knorr Kuhn)

Pull request description:

Remove unnecessary write access, and tighten the actors and conditions for the labeler and ci failures workflows


ACKs for top commit:
satsfy:
tACK 0c6f377
apoelstra:
ACK 0c6f37729b8f003a3af10e9f8c0ed00a12876200; successfully ran local tests


Tree-SHA512: 3799e0045ca5b5f4a788bf372fc4cd6f9ab78f191b90fe85773064a2ad21974ca684baaba62a08b844e9f90d6c7887c2b03ba721274546587634c460cc12628e

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationboot or update pathdocumentation-only discountmerge-commit duplicate discount
AI analysis · Low 37/100

This commit tightens three GitHub Actions workflows to reduce the risk of supply-chain or repository-manipulation attacks. It removes an unused high-power permission (id-token: write), makes a CI-failure issue-matching script only trust issues created by the GitHub Actions bot, and validates data pulled from untrusted pull-request workflow artifacts before using it to label or comment on pull requests. These are defensive hardening changes rather than fixes for a known active exploit.

Security candidateMerge rust-bitcoin/rust-bitcoin#7136: Release tracking PR: `internals 0.8.2`by Andrew Poelstra · d7bfa112 · Oct 30, 2026 · 20 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7136: Release tracking PR: `internals 0.8.2`

bb78d8841f92d836b9db76721eee5d86155c69f2 internals: Bump version to 0.8.2 (Tobin C. Harding)

Pull request description:

We meant to release #6974 in 0.8.1 but messed it up.

In preparation for release add a changelog entry, bump the version, and update the lock files.


ACKs for top commit:
apoelstra:
ACK bb78d8841f92d836b9db76721eee5d86155c69f2; successfully ran local tests


Tree-SHA512: 32dd46e95713907c47e00fc6cfbea35c115736e6c39ee986ecd26ca81717771d44432d08524299c92fa970a2f432729a81b6241c82d06e59ae86ec6b65e7583f

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit is a routine release-tracking merge that bumps the version of the `bitcoin-internals` crate from 0.8.1 to 0.8.2 and updates all dependent crates' version requirements and lock files. It contains no code changes, bug fixes, or security patches in the diff itself. The changelog notes that the actual functional change (rejecting a plus sign in certain number parsers) was supposed to ship in 0.8.1 but was accidentally omitted, so this release merely corrects that packaging mistake.

Security candidateMerge rust-bitcoin/rust-bitcoin#7129: primitives: Tidy docsby Andrew Poelstra · d1519949 · Oct 30, 2026 · 7 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7129: primitives: Tidy docs

c9d0274b3e186b8cc772929b0fe82635f38f6620 primitives: Add missing SPDX header (Jamil Lambert, PhD)
3cb4f669b2cf00cdc5e733bee8791c1394f5fbbd primitives: Add missing blank lines (Jamil Lambert, PhD)
b024399973c72eee8adbebf41d071ddbe766f870 primitives: Tidy doc wording (Jamil Lambert, PhD)
7376de3fb60084dde8b282d141ce44a6cc56fd10 primitives: Remove stale note about old atomics (Jamil Lambert, PhD)
72ee0e660ff9ec886c771af8605de2c619a4dcc2 primitives: Fix Witness::from_slice panics docs (Jamil Lambert, PhD)
6cf1d9b55a1e4cbd9143572d5c94574e17482378 primitives: Add missing full stops to docs (Jamil Lambert, PhD)

Pull request description:

A handful of doc fixes. The details are in each of the commit logs.

Docs only changes.


ACKs for top commit:
tcharding:
ACK c9d0274b3e186b8cc772929b0fe82635f38f6620
apoelstra:
ACK c9d0274b3e186b8cc772929b0fe82635f38f6620; successfully ran local tests


Tree-SHA512: 2fafc38e83b07a69dc16f43aaa276ede5216435e1d6b01c0a3b1c468ee1765f0f84a1b5175b0afd816d8c35e70442da0920be9bb04b6d5a8eee6205ff5a74707

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit is a documentation-only cleanup. It fixes typos, adds missing punctuation and blank lines, updates a panic description, removes a stale comment about old Rust atomics, and adds a missing SPDX license header. No executable code behavior was changed, so there is no security impact.

Security candidateinternals: Bump version to 0.8.2by Tobin C. Harding · bb78d884 · Oct 30, 2026 · 20 filesMessage 76 · AdequateInformational 15Details
Commit message · Tobin C. Harding

internals: Bump version to 0.8.2

We meant to release #6974 in 0.8.1 but messed it up.

In preparation for release add a changelog entry, bump the version,
and update the lock files.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit is purely a release housekeeping change. It bumps the version number of the `bitcoin-internals` crate from 0.8.1 to 0.8.2, updates dependency references across the workspace, refreshes lock files, and adds a changelog entry. The actual code change being released (rejecting a plus sign in certain number parsers) was merged earlier in pull request #6974 and is not present in this diff.

Security candidateRemove unused errors and variantsby Mitchell Bagot · 9b23b162 · Oct 29, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Mitchell Bagot

Remove unused errors and variants

With the changes to the FromStr trait impls on Xpub and Xpriv, the
InvalidBase58PayloadLength error variants and inner error type are no
longer needed. As such, they can be dropped to clean up the errors.

Remove InvalidBase58PayloadLengthError and InvalidBase58PayloadLength
error variants from ParseXp*Error.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit removes unused error types and variants from the BIP32 key parsing code. It is a cleanup change with no functional behavior change and no security impact.