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
279commits · 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 43 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.

Lower-priorityunits: correct relative locktime error docsby jrakibi · 0d289078 · Nov 6, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · jrakibi

units: correct relative locktime error docs

The docs refer to a non exisitng argument `chain_tip` while `LockTime::is_satisfied_by`
takes `chain_tip_height` and `chain_tip_mtp`.

Use the actual names and clarify the error condition better.

Also change "not after" to "less than", since `chain_tip_mtp` and
`utxo_prev_block_mtp` can be equal without causing an error.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityunits: use utxo_prev_block_mtp for relative time locksby jrakibi · d6eedc90 · Nov 6, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · jrakibi

units: use utxo_prev_block_mtp for relative time locks

`utxo_mined_at` suggests we are referring to the MTP of the block
containing the UTXO. According to BIP68, it is the MTP of the
preceding block.

Rename `utxo_mined_at` to `utxo_prev_block_mtp` to make this clear.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7165: Remove the `_export` module from units and primitivesby Andrew Poelstra · 38af295f · Nov 5, 2026 · 4 filesMessage 100 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7165: Remove the `_export` module from units and primitives

d45f6b05ee6ba9a887459748f5e5ba226d45f1a1 primitives: remove _export module (satsfy (Renato Britto))
debe7769b7e69ffaeb7a5e7976895e97eb17e440 units: remove _export module (satsfy (Renato Britto))

Pull request description:

Part of https://github.com/rust-bitcoin/rust-bitcoin/issues/4130.

This is a breaking change!

A macro body is pasted into the caller, so `core::fmt::Display` inside a macro means whatever `core` is at the call site, not ours crate's `core` (https://doc.rust-lang.org/reference/macros-by-example.html#hygiene). When the caller is another crate, that can go fail things we cannot test for, so it used to be that exported macros write `$crate::_export::_core` to force our own `core`.

However, units removed its last exported macros in https://github.com/rust-bitcoin/rust-bitcoin/pull/4886 and primitives never exported any, so neither module serves a macro anymore. In fact, I don't think we should ever put back a macro in them. So i removed that. I also confirmed that nowhere else is it applicable to remove this or add, by checking which crates have a `#[macro_export]` attribute.

I also searched public Rust code for `units::_export` and `primitives::_export`, nothing was found, so this PR has not broken any public user we know of, but it can break a private repo somewhere. But `hashes::_export::_core` does leak downstream though (e.g. [rust-lightning](https://github.com/lightningdevkit/rust-lightning/blob/main/lightning/src/onion_message/messenger.rs#L148), [mintlayer](https://github.com/mintlayer/bitcoin-rpc-api/blob/master/src/lib.rs#L36)), which shows the risk of keeping such a module: because it re-exports all of `core`, an IDE, for example, offers auto import of `bitcoin::hashes::_export::_core::time::Duration` next to `core::time::Duration`, users may pick in a moment of inattention, and every later move of the hidden module breaks their build.

This PR is not a technically a semver break, but our fix drops that prefix downstream users could, in theory, by relying on, which would break their compilation. If we ever remove it from hashes is would be a breaking change.

This change is also applicable to internals, but I can see a future in which it exports macros, and may potentially be moved to rust-bitcoin-maintainer-tools, so leave that as a follow up.


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


Tree-SHA512: 8745cea31121c24aeaa534316448f917fb8cbfc2fc0ab5cd2c62467f7fc0b97b739a861f9117bcf38f333a865b04e10056b0cd4c2d8bd3aac89c0af21014471f

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
merge-commit duplicate discount
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.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7164: units: finish relative height to block count rewordingby Andrew Poelstra · 474ad2f3 · Nov 5, 2026 · 10 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7164: units: finish relative height to block count rewording

7ed41a3c2ce6c65db693a7128661d886e12e7808 units: doc reword of height to block count (satsfy (Renato Britto))
dab7872c18a5c9d4313cc867e5fa2719f591df76 units: rename TooBigForRelativeHeightError (satsfy (Renato Britto))

Pull request description:

Follow up of https://github.com/rust-bitcoin/rust-bitcoin/pull/7110. Renames the last error type still saying `height` and fixes the docs and error string that slipped through.

If I had done my job right in https://github.com/rust-bitcoin/rust-bitcoin/pull/7110, https://github.com/rust-bitcoin/rust-bitcoin/pull/6689 and https://github.com/rust-bitcoin/rust-bitcoin/pull/6671, this would not need to exist.


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


Tree-SHA512: 26d074c81208a13d906403553b8a87d85ecf88d5d8b672f5e664da5c123e2caecf83d7e9fd13fc777c42e2b946a2eb3da3e82b5fe7371c3007faa608f2f31263

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
merge-commit duplicate discount
Lower-priorityprimitives: remove _export moduleby satsfy (Renato Britto) · d45f6b05 · Nov 5, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · satsfy (Renato Britto)

primitives: remove _export module

primitives exports no macros, so the core re-export has no
use here.

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Lower-priorityunits: doc reword of height to block countby satsfy (Renato Britto) · 7ed41a3c · Nov 5, 2026 · 6 filesMessage 68 · AdequateTriage 0Details
Commit message · satsfy (Renato Britto)

units: doc reword of height to block count

Relative locktime wording moved from height to block count
(NumberOfBlocks), these docs and one error string still said
height.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityunits: remove _export moduleby satsfy (Renato Britto) · debe7769 · Nov 5, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · satsfy (Renato Britto)

units: remove _export module

units exports no macros, so the core re-export has no use.

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
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.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7157: units: clarify MTP args for relative locktimesby Andrew Poelstra · 8a7bd539 · Nov 5, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7157: units: clarify MTP args for relative locktimes

04d94815f309526b73a1d6caa56664544edca408 units: clarify MTP args for relative locktimes (jrakibi)

Pull request description:

The name `utxo_mined_at` suggests that we should use the MTP of the block that confirmed the UTXO. However according to BIP68, we should use the MTP of the preceding block:

BIP-68 spec :
> The timespan starts from the median-time-past of the output’s previous block, and ends at the MTP of the previous block

Renaming `utxo_mined_at` to something like `utxo_start_mtp` or `utxo_prev_block_mtp` would make this clearer. For now, I’ve only clarified the docs, pending agreement on whether to rename the parameter.


ACKs for top commit:
satsfy:
ACK 04d94815f309526b73a1d6caa56664544edca408
tcharding:
ACK 04d94815f309526b73a1d6caa56664544edca408
apoelstra:
ACK 04d94815f309526b73a1d6caa56664544edca408; successfully ran local tests


Tree-SHA512: 0e85ed800bc9073f96e7f7699cb3caa6fef4216a76e9e272043ace8ad933530fa0eac979ebbe0cd5d2391c5c6809636db4170834c7d1be9517f3a4771846e0c0

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
merge-commit duplicate discount
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7158: bip158: Fix minor nits across the crateby Andrew Poelstra · 3bd5ecd9 · Nov 5, 2026 · 3 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7158: bip158: Fix minor nits across the crate

4764de9d54b3635fbea5af7400b910ad79a066cd bitcoin_bip158: Remove pub from modules in a private module (Abeeujah)
5b0dbfe81306cfadc5b4cd043aab477a96d280b5 bitcoin_bip158: Add is_empty and element_count accessor methods (Abeeujah)
66bffdf720d362f5b815f0651f861c8142728041 bitcoin_bip158: Align squished up text in source code (Abeeujah)
798cf2fe51be278b55405fa9a4621d227e0e1d46 bitcoin_bip158: Propagate primitives/std when std is enabled (Abeeujah)
a824023ae656ff5464fb3778ecfb46cc92112377 bitcoin_bip158: Fix FilterHeaderDecoder::new doc comment (Abeeujah)

Pull request description:

- Patch 1 fixes the `FilterHeaderDecoder::new` doc comment which points to `FilterHash` instead of `FilterHeader`.
- Patch 2 forward propagates `primitves/std` in `bip158` when `std` feature is enabled.
- Patch 3 formats squished up text to be more legible.
- Patch 4 adds `is_empty` and `element_count` accessor methods to `BasicFilter`.
- Patch 5 removes the `pub` visibility from the `error` modules defined in both `hash_types` and `filter` modules which are private scoped in the crate's root/lib.rs.


ACKs for top commit:
apoelstra:
ACK 4764de9d54b3635fbea5af7400b910ad79a066cd; successfully ran local tests; these all seem reasonable, though I'm unsure if `is_empty()` can differ from `as_bytes().is_empty()` which might be surprising, and I forget where we landed on the "propagating `std` feature" discussion
tcharding:
ACK 4764de9d54b3635fbea5af7400b910ad79a066cd


Tree-SHA512: 9deeb9049bdc14bec07dd9e2c577aa51cc264ec3bf9a602950dc36e5b4603addcb64d14f5f6269569479eadbac72531d69036be8c072b7ccad8114148a99a066

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
merge-commit duplicate discount
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.

Lower-priorityci: take baseline from merge baseby satsfy (Renato Britto) · cda30cd4 · Nov 4, 2026 · 2 filesMessage 80 · StrongTriage 0Details
Commit message · satsfy (Renato Britto)

ci: take baseline from merge base

pull_request.base.sha is not updated when master moves, so
old PRs got master changes reported as their own API diffs
and semver breaks.

Now we use `git merge-base` with the PRs commit against
the master commit in which PR is merged onto. This works
both in GitHub and Forgejo CI.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7155: p2p: fix V1 decoder framingby Andrew Poelstra · 94c6f791 · Nov 4, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7155: p2p: fix V1 decoder framing

a67bedc2d763f521dbf6957b02e2e8b6a098755f p2p: split off a network message decoder error shared by v1 and v2 (Nick Johnson)
947dde88f7392484ba1ca0a2833e084bbb885a9b p2p: rename v1 decoder state and variants for symmetry with v2 (Nick Johnson)
fd5aa8357b9b9c40ddc9caf0e4f5f311e7de1a79 p2p: unit tests for v1 for V1 framing clamp and V2 unknown round-trip (Nick Johnson)
fde6d6f9ecdedb7d0045514c20eff70b068d7dce p2p: fix V1 framing over-read and refactor decoder hierarchy (Nick Johnson)

Pull request description:

This fixes three issues reported by the red-team, in particular, knorrium.

The first commit holds the decoder reorganization and logic fixes. The second commit has unit tests for the fixed logic. The last two commits are purely cosmetic, but I think help follow the code a lot better.

The first issue was that the V1 decoder never enforced the V1 header's payload length. This makes it possible to send a header payload length 0 (or anything) and then just keep streaming over valid chunks of data (e.g. transactions). The first commit centralizes all the V1 framing into the V1 decoder (instead of spread across 2 decoders, the second of which was bypassed by V2 anyways). For V1 decoding, the header's payload length is now enforced. For V2 decoding, this framing will have to be done in the BIP-324 transport level where the length is known.

The second issue fixed is V2 encoding/decoding handling the `Unknown` variant roundtrip. And the third is not allocating the entire `Unknown` buffer upfront.


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


Tree-SHA512: b63353ac127e9571bf83712edab980f17934e4245759a436097f8b8c52084b12d326568667f7fb7872fcb82ac5746278097fc47ccabc3f6d38a174c57b2cf65b

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
merge-commit duplicate discount
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7154: units: document absolute locktime boundaryby Andrew Poelstra · abc06819 · Nov 4, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7154: units: document absolute locktime boundary

6a5df110670c33be621cd90699edc6f5aaab5528 units: document absolute locktime boundary (satsfy (Renato Britto))

Pull request description:

Close https://github.com/rust-bitcoin/rust-bitcoin/issues/3318

The issue brings up the simple point that our `LockTime` variant docs never specifiy if a tx lock set to height h allows inclusion in block h+1, or equivalent for time locks.


ACKs for top commit:
tcharding:
ACK 6a5df110670c33be621cd90699edc6f5aaab5528
jrakibi:
ACK 6a5df110670c33be621cd90699edc6f5aaab5528


Tree-SHA512: 1c637598688640d04253f220ff678457465a7663c78913accb21a25ddea3a9d21449b97e1c687a608eb2f9ab233237a455049e6a4bb357db567712311d3451f8

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
merge-commit duplicate discount
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.

Lower-priorityMerge rust-bitcoin/rust-bitcoin#7152: Manual update to cargo-rbmt (to 0.5.4)by Andrew Poelstra · ea3a7fea · Nov 3, 2026 · 1 fileMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7152: Manual update to cargo-rbmt (to 0.5.4)

c5ec682ee5f88601abacf3d331be0bae76749eb2 ci: declare lockfiles for rbmt 0.5.4 (satsfy (Renato Britto))
f9c6d7de17d94909952249f25ca7e81d2f9fcbd6 Automated update to cargo-rbmt-0.5.4 (Update RBMT Bot)

Pull request description:

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

Rbmt 0.5.4 defaults declared lockfiles to minimal and maximum when the workspace declares none. This repo tracks minimal and recent, which caused lint, docs and api to fail restoring `Cargo-maximum.lock`.


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


Tree-SHA512: 0e97438f2e63de7d1e127a1bd302743ebf4b6c633ccc30ef076ed812b60a9295818fab13e816efb0f592a01dbd7485ad91ace8052555c08c7fff231a9cd471d3

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
merge-commit duplicate discount
Lower-priorityp2p: split off a network message decoder error shared by v1 and v2by Nick Johnson · a67bedc2 · Nov 3, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Nick Johnson

p2p: split off a network message decoder error shared by v1 and v2

This should be further improved by adding more context to the failure.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityp2p: rename v1 decoder state and variants for symmetry with v2by Nick Johnson · 947dde88 · Nov 3, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Nick Johnson

p2p: rename v1 decoder state and variants for symmetry with v2

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge rust-bitcoin/rust-bitcoin#7149: poly1305: Add 4 block processing on aarch64by Andrew Poelstra · e0e7f0c2 · Nov 3, 2026 · 2 filesMessage 91 · StrongTriage 0Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7149: poly1305: Add 4 block processing on aarch64

20af2924c977e3258b37440f4c21af9ecc227c07 poly1305: Add 4 block processing on aarch64 (rustaceanrob)

Pull request description:

Add the same algorithm as 522f71f629cd8a814de72078c4dfda990fdfdadf on aarch64.

256 bit registers are not available, so the multiplication in `dot5` is split over the two pairs of two block SIMD. By interleving the instructions the compiler should still be able to use all available registers.

<details>
<summary>Benchmarks</summary>

```
chacha20poly1305/encrypt_no_aad/128
time: [414.63 ns 415.43 ns 416.33 ns]
thrpt: [293.21 MiB/s 293.84 MiB/s 294.41 MiB/s]
change:
time: [−5.0574% −4.8126% −4.5835%] (p = 0.00 < 0.05)
thrpt: [+4.8036% +5.0559% +5.3268%]
Performance has improved.
Found 3 outliers among 100 measurements (3.00%)
1 (1.00%) high mild
2 (2.00%) high severe
chacha20poly1305/encrypt_with_aad/128
time: [433.30 ns 433.64 ns 434.06 ns]
thrpt: [281.23 MiB/s 281.50 MiB/s 281.72 MiB/s]
change:
time: [−7.1525% −6.4452% −5.8659%] (p = 0.00 < 0.05)
thrpt: [+6.2314% +6.8893% +7.7035%]
Performance has improved.
Found 8 outliers among 100 measurements (8.00%)
3 (3.00%) high mild
5 (5.00%) high severe
chacha20poly1305/decrypt_ok/128
time: [435.92 ns 436.18 ns 436.47 ns]
thrpt: [279.67 MiB/s 279.86 MiB/s 280.03 MiB/s]
change:
time: [−5.0212% −4.8548% −4.6425%] (p = 0.00 < 0.05)
thrpt: [+4.8685% +5.1025% +5.2866%]
Performance has improved.
Found 4 outliers among 100 measurements (4.00%)
2 (2.00%) high mild
2 (2.00%) high severe
chacha20poly1305/encrypt_no_aad/1024
time: [950.51 ns 953.62 ns 956.64 ns]
thrpt: [1020.8 MiB/s 1.0001 GiB/s 1.0033 GiB/s]
change:
time: [−42.664% −42.487% −42.320%] (p = 0.00 < 0.05)
thrpt: [+73.369% +73.875% +74.410%]
Performance has improved.
chacha20poly1305/encrypt_with_aad/1024
time: [971.96 ns 975.13 ns 978.35 ns]
thrpt: [998.18 MiB/s 1001.5 MiB/s 1004.7 MiB/s]
change:
time: [−41.042% −40.885% −40.722%] (p = 0.00 < 0.05)
thrpt: [+68.695% +69.162% +69.612%]
Performance has improved.
Found 1 outliers among 100 measurements (1.00%)
1 (1.00%) high mild
chacha20poly1305/decrypt_ok/1024
time: [974.53 ns 976.51 ns 978.25 ns]
thrpt: [998.28 MiB/s 1000.1 MiB/s 1002.1 MiB/s]
change:
time: [−40.520% −40.388% −40.248%] (p = 0.00 < 0.05)
thrpt: [+67.359% +67.752% +68.123%]
Performance has improved.
Found 22 outliers among 100 measurements (22.00%)
9 (9.00%) low severe
8 (8.00%) low mild
2 (2.00%) high mild
3 (3.00%) high severe
chacha20poly1305/encrypt_no_aad/16384
time: [11.736 µs 11.757 µs 11.779 µs]
thrpt: [1.2954 GiB/s 1.2978 GiB/s 1.3002 GiB/s]
change:
time: [−50.897% −50.715% −50.563%] (p = 0.00 < 0.05)
thrpt: [+102.28% +102.90% +103.65%]
Performance has improved.
Found 8 outliers among 100 measurements (8.00%)
1 (1.00%) low severe
4 (4.00%) low mild
1 (1.00%) high mild
2 (2.00%) high severe
chacha20poly1305/encrypt_with_aad/16384
time: [11.712 µs 11.730 µs 11.750 µs]
thrpt: [1.2986 GiB/s 1.3009 GiB/s 1.3029 GiB/s]
change:
time: [−53.995% −53.271% −52.649%] (p = 0.00 < 0.05)
thrpt: [+111.19% +114.00% +117.37%]
Performance has improved.
Found 23 outliers among 100 measurements (23.00%)
10 (10.00%) low severe
5 (5.00%) low mild
1 (1.00%) high mild
7 (7.00%) high severe
chacha20poly1305/decrypt_ok/16384
time: [11.734 µs 11.748 µs 11.763 µs]
thrpt: [1.2972 GiB/s 1.2989 GiB/s 1.3004 GiB/s]
change:
time: [−52.537% −52.305% −52.083%] (p = 0.00 < 0.05)
thrpt: [+108.70% +109.66% +110.69%]
Performance has improved.
Found 10 outliers among 100 measurements (10.00%)
6 (6.00%) low mild
2 (2.00%) high mild
2 (2.00%) high severe
chacha20poly1305/encrypt_no_aad/65536
time: [46.408 µs 46.436 µs 46.465 µs]
thrpt: [1.3136 GiB/s 1.3144 GiB/s 1.3152 GiB/s]
change:
time: [−51.823% −51.658% −51.491%] (p = 0.00 < 0.05)
thrpt: [+106.15% +106.86% +107.57%]
Performance has improved.
Found 12 outliers among 100 measurements (12.00%)
7 (7.00%) low severe
2 (2.00%) low mild
3 (3.00%) high severe
chacha20poly1305/encrypt_with_aad/65536
time: [46.445 µs 46.483 µs 46.517 µs]
thrpt: [1.3121 GiB/s 1.3131 GiB/s 1.3141 GiB/s]
change:
time: [−50.960% −50.871% −50.778%] (p = 0.00 < 0.05)
thrpt: [+103.16% +103.54% +103.91%]
Performance has improved.
Found 9 outliers among 100 measurements (9.00%)
4 (4.00%) low severe
1 (1.00%) low mild
1 (1.00%) high mild
3 (3.00%) high severe
chacha20poly1305/decrypt_ok/65536
time: [46.362 µs 46.394 µs 46.424 µs]
thrpt: [1.3147 GiB/s 1.3156 GiB/s 1.3165 GiB/s]
change:
time: [−52.383% −51.870% −51.503%] (p = 0.00 < 0.05)
thrpt: [+106.20% +107.77% +110.01%]
Performance has improved.
Found 8 outliers among 100 measurements (8.00%)
2 (2.00%) low severe
2 (2.00%) low mild
1 (1.00%) high mild
3 (3.00%) high severe
```
</details>

Assisted-by: Claude Opus 5.5


ACKs for top commit:
jrakibi:
ACK 20af2924c977e3258b37440f4c21af9ecc227c07
apoelstra:
ACK 20af2924c977e3258b37440f4c21af9ecc227c07; successfully ran local tests


Tree-SHA512: f43ac3a2c6b0ccac019eda30848bf4786f04c1c9f362da47bff4f2d76e90a7eb6a4e1ed21a151c6ba1f7b70b6f2ffc61bab90da2034d856c0c9dc2b02e58b823

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
merge-commit duplicate discount
Lower-priorityp2p: unit tests for v1 for V1 framing clamp and V2 unknown round-tripby Nick Johnson · fd5aa835 · Nov 3, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Nick Johnson

p2p: unit tests for v1 for V1 framing clamp and V2 unknown round-trip

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityp2p: fix V1 framing over-read and refactor decoder hierarchyby Nick Johnson · fde6d6f9 · Nov 3, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Nick Johnson

p2p: fix V1 framing over-read and refactor decoder hierarchy

The V1 decoder's push_bytes now clamps input to the header's
declared payload_len, preventing a malicious peer from streaming
unbounded data past a short declared length. Credit to the bitcoin
red-team for finding this dos vector, in particular Felipe Knorr Kuhn
(knorrium).

The existing `NetworkMessageDecoder` was folded int the V1 decoder,
so all V1 framing logic is concentrated where you would expect to find
it. `NetworkMessageDecoderInner` was renamed to `NetworkMessageDecoder`
and is the canonical payload decdoer for both V1 and V2 decoders.

The V2 framing layer is up higher in the BIP-324 packet transport
protocol, so `V2NetworkMessageDecoder` is not self-delimiting for the
Unknown network message variant. The BIP-324 packet decoder must handle
this case.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityci: declare lockfiles for rbmt 0.5.4by satsfy (Renato Britto) · c5ec682e · Nov 3, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · satsfy (Renato Britto)

ci: declare lockfiles for rbmt 0.5.4

rbmt 0.5.4 defaults to minimal and maximum lockfiles when
the workspace declares none. This repo tracks minimal
and recent.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI review queuedMerge rust-bitcoin/rust-bitcoin#7148: build(deps): bump taiki-e/install-action from 2.86.8 to 2.87.4by Andrew Poelstra · 677e9232 · Nov 2, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra

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

87f8832e8f86941d8c1b8504a901e33b867b1c7a build(deps): bump taiki-e/install-action from 2.86.8 to 2.87.4 (dependabot[bot])

Pull request description:

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.86.8 to 2.87.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p>
<blockquote>
<h2>2.87.4</h2>
<ul>
<li>
<p>Update <code>uv@latest</code> to 0.12.8.</p>
</li>
<li>
<p>Update <code>protoc@latest</code> to 3.36.1.</p>
</li>
<li>
<p>Update <code>coreutils@latest</code> to 0.11.0.</p>
</li>
</ul>
<h2>2.87.3</h2>
<ul>
<li>
<p>Update <code>zizmor@latest</code> to 1.30.0.</p>
</li>
<li>
<p>Update <code>ubi@latest</code> to 0.12.0.</p>
</li>
<li>
<p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.25.8.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.8.16.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.1.0.</p>
</li>
<li>
<p>Update <code>dprint@latest</code> to 0.57.0.</p>
</li>
</ul>
<h2>2.87.2</h2>
<ul>
<li>
<p>Update <code>typos@latest</code> to 1.50.0.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.5.0.</p>
</li>
<li>
<p>Update <code>shfmt@latest</code> to 3.14.0.</p>
</li>
</ul>
<h2>2.87.1</h2>
<ul>
<li>
<p>Update <code>uv@latest</code> to 0.12.7.</p>
</li>
<li>
<p>Update <code>typos@latest</code> to 1.49.1.</p>
</li>
<li>
<p>Update <code>syft@latest</code> to 1.51.1.</p>
</li>
<li>
<p>Update <code>prek@latest</code> to 0.5.0.</p>
</li>
<li>
<p>Update <code>d2@latest</code> to 0.8.2.</p>
</li>
<li>
<p>Update <code>cargo-zigbuild@latest</code> to 0.23.3.</p>
</li>
<li>
<p>Update <code>cargo-rdme@latest</code> to 2.2.2.</p>
</li>
<li>
<p>Update <code>biome@latest</code> to 2.5.11.</p>
</li>
</ul>
<h2>2.87.0</h2>
<ul>
<li>
<p>Support <code>kache</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/1980">#1980</a>, thanks <a href="https://github.com/ChrisJr404"><code>@​ChrisJr404</code></a>)</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.30.1.</p>
</li>
<li>
<p>Update <code>uv@latest</code> to 0.12.6.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<p>All notable changes to this project will be documented in this file.</p>
<p>This project adheres to <a href="https://semver.org">Semantic Versioning</a>.</p>
<!-- raw HTML omitted -->
<h2>[Unreleased]</h2>
<h2>[2.89.0] - 2026-11-01</h2>
<ul>
<li>
<p>Support <code>yq</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/2036">#2036</a>, thanks <a href="https://github.com/FirelightFlagboy"><code>@​FirelightFlagboy</code></a>)</p>
</li>
<li>
<p>Support <code>mold</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/2044">#2044</a>, thanks <a href="https://github.com/FirelightFlagboy"><code>@​FirelightFlagboy</code></a>)</p>
</li>
<li>
<p>Fix an error when old cargo-binstall had already been installed at non-standard location. (<a href="https://redirect.github.com/taiki-e/install-action/pull/2048">#2048</a>)</p>
</li>
<li>
<p>Update <code>wasm-tools@latest</code> to 1.263.0.</p>
</li>
<li>
<p>Update <code>wasm-pack@latest</code> to 0.15.1.</p>
</li>
<li>
<p>Update <code>wasm-bindgen@latest</code> to 0.2.130.</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.36.1.</p>
</li>
<li>
<p>Update <code>prek@latest</code> to 0.5.9.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.10.25.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.16.0.</p>
</li>
<li>
<p>Update <code>cargo-binstall@latest</code> to 1.26.2.</p>
</li>
</ul>
<h2>[2.88.1] - 2026-10-30</h2>
<ul>
<li>
<p>Update <code>wasmtime@latest</code> to 50.0.1.</p>
</li>
<li>
<p>Update <code>vacuum@latest</code> to 0.36.0.</p>
</li>
<li>
<p>Update <code>tombi@latest</code> to 1.9.8.</p>
</li>
<li>
<p>Update <code>mise@latest</code> to 2026.10.23.</p>
</li>
<li>
<p>Update <code>kingfisher@latest</code> to 2.15.0.</p>
</li>
<li>
<p>Update <code>espup@latest</code> to 0.19.0.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taiki-e/install-action/commit/e67fa11c4b9316fa714ddf0abed07a0c3143b95b"><code>e67fa11</code></a> Release 2.87.4</li>
<li><a href="https://github.com/taiki-e/install-action/commit/b2a993f9717f6183aa0414e61c39a77ba640b0d1"><code>b2a993f</code></a> Update <code>uv@latest</code> to 0.12.8</li>
<li><a href="https://github.com/taiki-e/install-action/commit/646c3cb94da594e9ad1ba71ce25af2b846a32592"><code>646c3cb</code></a> Update <code>protoc@latest</code> to 3.36.1</li>
<li><a href="https://github.com/taiki-e/install-action/commit/c7a42ecced74789ccdb74389f34cd393a1c6ea74"><code>c7a42ec</code></a> Update <code>coreutils@latest</code> to 0.11.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/b585865916acbc68660bff68f147e29cdd51742f"><code>b585865</code></a> Update cargo-deb manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/0758d235715de2f3551eacc980d9ae8fce9342c3"><code>0758d23</code></a> Release 2.87.3</li>
<li><a href="https://github.com/taiki-e/install-action/commit/88efe43bfd45d48641dfceaa8d61d410c820021a"><code>88efe43</code></a> Update <code>zizmor@latest</code> to 1.30.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/2880e0286789726ce93d833e73f37a1465d1299a"><code>2880e02</code></a> Update uv manifest</li>
<li><a href="https://github.com/taiki-e/install-action/commit/64a78f77b5812aa8c129138b11e9b96df3b9228f"><code>64a78f7</code></a> Update <code>ubi@latest</code> to 0.12.0</li>
<li><a href="https://github.com/taiki-e/install-action/commit/bc9ef8893585745dfab4c8f76b36bb67f1d2a47f"><code>bc9ef88</code></a> Update typos manifest</li>
<li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/fcf5432d9f50d67e37ee6e29bdb7a224ff67b4a7...e67fa11c4b9316fa714ddf0abed07a0c3143b95b">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=taiki-e/install-action&package-manager=github_actions&previous-version=2.86.8&new-version=2.87.4)](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:
apoelstra:
ACK 87f8832e8f86941d8c1b8504a901e33b867b1c7a; successfully ran local tests
satsfy:
ACK 87f8832e8f86941d8c1b8504a901e33b867b1c7a


Tree-SHA512: 46c9d828a9cd22092dd0c39aef65f4a6268d1140ea70091704d816021111359d5debb7fd2822e61dff4784025429372e40af39110a6ddb4b35317d5e696bb04a

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
documentation-only discountautomated dependency-update discountmerge-commit duplicate discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine Dependabot update that changes the version of a third-party GitHub Action (taiki-e/install-action) used in two automated workflow files. The action installs developer tools like cargo-mutants during CI testing. There is no indication in the commit or its description that this fixes a security vulnerability, and the change does not touch the project's actual Bitcoin library code.

AI review queuedMerge rust-bitcoin/rust-bitcoin#7075: ci: cache dependency build artifacts in the Test jobby Andrew Poelstra · 21434579 · Nov 2, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra

Merge rust-bitcoin/rust-bitcoin#7075: ci: cache dependency build artifacts in the Test job

14ac9eae30ef8f3d2907fc70507b4fb8b0e6393b ci: cache dependency build artifacts in the Test job (PeterXMR)

Pull request description:

Caches third-party build artifacts for the Test job, the remaining
dependency-caching item from #6951. The cache is saved only on pushes to
master and workspace artifacts are pruned before saving, so the cached
size stays limited to dependencies.

This patch was written with LLM assistance and reviewed by me.


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


Tree-SHA512: 81cc0238793654f98a3b6a512e3c42dc7def2620eb8bdb464e73b9c53ab9ead68ee0224668813de7516096bb7a8cc3190fdceb577420d1da1f0a6c53423670c2

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
documentation-only discountmerge-commit duplicate discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This commit only changes the project's GitHub Actions CI workflow to cache third-party dependency build artifacts during automated testing. It does not modify any library code, cryptographic logic, network handling, or user-facing behavior. There is no apparent security vulnerability introduced by this change.