CommitWatch RSS
RB
← All projectsRust Bitcoin

rust-bitcoin

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

BitcoinCryptographic librariesNormal
Source repository ↗
Repository coverage

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

459security candidates448second-pass queue199AI analyses
194commits · 30 days
405commits · 60 days
1283commits · 180 days
2070commits · 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.

64/100 average clarity
311Strong · 80–100
1054Adequate · 60–79
555Thin · 40–59
150Opaque · 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.
Mitchell Bagot64019288068
Tobin C. Harding4096528063
jrakibi94499068
Nick Johnson189203059
Andrew Poelstra51209075
Jamil Lambert, PhD114184061
Fmt Bot311411045
Trevor Arjeski111110069
Shing Him Ng3174056
Ismail Daif2263050
satsfy (Renato Britto)1766066
Martin Habovstiak2754069
Analysis record

Published AI watches

Last scanned 43 minutes ago

Informational 17 AI analysisMessage 80 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

refactor(bip32): Xpub child tweak api

This commit is a straightforward API refactor in the BIP-32 (Bitcoin key derivation) code. It replaces a function that returned a raw secret key and chain code with one that returns a new structured type called XpubChildTweak. The actual c…

No security-relevant behavioral change observedAPI rename and return-type encapsulation onlyNo new validation, bounds checking, or constant-time guarantees added
37191717by Trevor Arjeski+21−71 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 85 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

refactor(bip32): rename Xpub and Xpriv derivation methods

This is a routine code cleanup in a Bitcoin library. It renames key-derivation methods on extended public and private keys (Xpub/Xpriv) to clearer names and removes old aliases. There is no security bug being fixed and no new vulnerability…

No security-relevant logic changePure API renaming/refactoringDeprecated method removal may break downstream callers at compile time
f8f053fdby Trevor Arjeski+61−852 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add try_push to Buffer trait

This commit adds a new `try_push` method to an internal `Buffer` trait used during Base58 encoding. It is a straightforward, additive change that lets encoding code gracefully handle a full fixed-size buffer in no-allocation builds. There …

aafb6065by Mitchell Bagot+15−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

consensus_encoding: Rename _with decoder functions

This commit is a simple renaming of internal Rust functions from names ending in '_with' to names ending in '_with_decoder'. It does not change what the code does, only what the functions are called, to avoid confusion with another functio…

12325a67by Mitchell Bagot+18−174 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

2026-07-05 automated rustfmt nightly

This commit is a routine automated code-formatting run by the rustfmt tool. It only changes whitespace, import order, and line breaks in five files. There are no functional changes, no bug fixes, and no security-related modifications.

673e5ee4by Fmt Bot+12−115 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 95 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

ci: adapt default and no feature bip32 test for rbmt 0.4.0

This is a routine update to the project's automated testing configuration. A tool used to run example tests changed its syntax, so the developer updated one line to keep the same tests running the same way. There is no user-facing change a…

5f933d5cby satsfy (Renato Britto)+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add From/TryFrom for Signature/SerializedSignature

This commit adds standard Rust conversion traits (From/TryFrom) between an ECDSA signature and its serialized byte form. It is a small API-consistency change that mirrors traits already present on the Taproot signature type. There is no in…

No security-relevant keywords in commit title or messageNo changes to cryptographic validation or parsing logicOnly adds convenience trait implementations delegating to existing methods
3cf8c405by Mitchell Bagot+21−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 83 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add {Lower,Upper}Hex to ecdsa::Signature

This commit adds new ways to print ECDSA Bitcoin signatures as hexadecimal text (lowercase and uppercase), matching formatting already available for Taproot signatures. It also makes the existing Display implementation reuse the new LowerH…

69540f98by Mitchell Bagot+43−51 file
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 90 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Replace Signature Display with call to SerializedSignature

This commit fixes a formatting bug in how Bitcoin ECDSA signatures are printed as text. Previously, the signature was printed in two separate pieces (the DER-encoded signature and the sighash byte), which could mishandle formatting options…

Incorrect format-flag handling in Display implBehavioral inconsistency between Signature::fmt and SerializedSignature::fmtRegression test added for format-string parity
c8ee6361by Mitchell Bagot+18−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add PartialOrd, Ord to ecdsa::Signature

This commit simply adds standard sorting traits (PartialOrd and Ord) to an ECDSA signature type and its associated sighash type, matching what already exists for similar types. There is no indication this fixes or introduces a security pro…

1e020732by Mitchell Bagot+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Remove PrivateKeyExt and make PrivateKey::as_inner private

This commit is a routine API cleanup, not a security fix. It removes a helper trait called PrivateKeyExt and hides a low-level accessor method (as_inner) that exposes the underlying secret key object. The same signing behavior is preserved…

Reduction of public API surface for secret-key materialRemoval of extension trait that exposed raw ECDSA recoverable signingas_inner accessor narrowed from pub to pub(super)
e9ea66a1by Mitchell Bagot+14−344 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 57 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

refactor: split bip32 xkey parse errors

This commit is a code cleanup: it splits one big error type into several smaller, more specific error types for BIP-32 extended key parsing. It does not change what the code accepts or rejects, only how errors are named and organized. Ther…

55ef86a2by Trevor Arjeski+214−771 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

style: reorder bip32 error impls

This commit is a pure code-style change. It reorders the implementation blocks for several error types in a Bitcoin-related Rust library so that the order of traits (From, std::error::Error, Display, helper methods) is consistent. No logic…

78a3ac3fby Trevor Arjeski+38−381 file
No security note in commit
Open full analysis →Source commit ↗
Informational 11 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Remove Encodable and Decodable impls for crate types

This commit removes old serialization/deserialization trait implementations (called Encodable and Decodable) from many Bitcoin data types in the rust-bitcoin library. It is described by the project as a cleanup step toward replacing the ol…

Large deletion of serialization code (535 lines removed)Removal of consensus encoding traits from core Bitcoin typesRemoval of transaction deserialization tests including extreme-size witness/scriptSig tests
6f136cdfby Mitchell Bagot+8−53512 files
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Replace uses of bitcoin::consensus with consensus_encoding

This commit swaps out an older Bitcoin data-encoding system for a newer one across six files. It is a routine internal refactoring change. There is no direct evidence in the commit that it fixes a security vulnerability, but any encoding c…

Refactor of consensus-critical serialization code (sighash, taproot leaf hash, BIP-158 filters, consensus validation)Change of compact-size encoder/decoder implementation and error typesRemoval of `bitcoin::consensus` dependency from several modules
22cf8fb6by Mitchell Bagot+38−356 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Replace uses of consensus in tests

This commit only changes test code and documentation examples in the rust-bitcoin library. It replaces older consensus encoding/decoding helper functions with newer equivalents from a different internal module. There is no change to produc…

171f6661by Mitchell Bagot+81−697 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add XOnlyPublicKey::verify

This commit adds a new convenience method, XOnlyPublicKey::verify, that lets users verify Schnorr (taproot) signatures without calling the underlying secp256k1 library directly. It is a straightforward API addition with no obvious security…

New public API surface for signature verificationWraps secp256k1::schnorr::verify without altering verification semanticsNo input parsing, no secret-key handling, no allocator changes
8a5deee2by Mitchell Bagot+28−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 83 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add tests to verify 0 return for overflow

This commit only adds new unit tests to verify that a previously changed function, Target::from_compact, returns zero when a Bitcoin 'compact' difficulty value overflows a 256-bit target. It does not change any production code. The tests c…

4ee43312by Mitchell Bagot+17−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Return 0 on Target::from_compact overflow

This commit fixes a bug in how rust-bitcoin converts Bitcoin 'compact' difficulty targets into full numeric Target values. Previously, if the compact value encoded a number too large to fit in a valid Target, the code would silently produc…

Consensus-critical code path modifiedOverflow/wraparound in cryptographic/numeric conversionAlignment with Bitcoin Core behavior (SetCompact overflow flag)
1fb9a651by Mitchell Bagot+7−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 57 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

refactor: split bip32 path parse errors

This commit is a code cleanup (refactor) that splits one combined error type into two separate error types for parsing BIP32 derivation paths. It does not change the actual parsing rules or fix any security bug. It only changes how error m…

22a4cbc6by Trevor Arjeski+68−291 file
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

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

AI review queuedunits: make Sequence inner field privateby satsfy (Renato Britto) · 30f280da · Jul 29, 2026 · 6 filesMessage 68 · AdequateTriage 12Details
Commit message · satsfy (Renato Britto)

units: make Sequence inner field private

The public inner field violates C-STRUCT-PRIVATE. The value is already
accessible through `from_consensus` and `to_consensus_u32` so nothing
is lost by hiding the field.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
Lower-priorityunits: remove Default from Sequenceby satsfy (Renato Britto) · 944f7f21 · Jul 29, 2026 · 7 filesMessage 78 · AdequateTriage 5Details
Commit message · satsfy (Renato Britto)

units: remove Default from Sequence

The Sequence gets the Default trait but misses a `new()` function.

Remove the Sequence's Default and drop Sequence from the conformance tests,
the API snapshots and give the fuzz wrapper an explicit default instead.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidence
Lower-priorityprimitives: Apply the witness item size limit to every elementby Kyle 🐆 · 67d30d2c · Jul 29, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Kyle 🐆

primitives: Apply the witness item size limit to every element

Assisted-by: Claude Opus 5

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityunits: Restore the +1 in relative locktime satisfied by heightby Kyle 🐆 · ee13c6bb · Jul 29, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Kyle 🐆

units: Restore the +1 in relative locktime satisfied by height

Assisted-by: Claude Opus 5

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityci: merge check-semver scripts into oneby Nick Johnson · 2be88754 · Jul 28, 2026 · 4 filesMessage 72 · AdequateTriage 0Details
Commit message · Nick Johnson

ci: merge check-semver scripts into one

Clean up a lot of the handling by leveraging check-semver features. This
allows the script to handle the semver trick.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritychacha20_poly1305: bump version to 0.2.1by Nick Johnson · 1657a23a · Jul 28, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · Nick Johnson

chacha20_poly1305: bump version to 0.2.1

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityprimitives: Add serde note to crate docsby Mitchell Bagot · 35d2bbd5 · Jul 28, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Mitchell Bagot

primitives: Add serde note to crate docs

Currently, the consensus encodable types in primitives don't have
serde trait implementations, and are instead supposed to be used with
consensus_encoding's serde_as_consensus module. However, this is not
documented anywhere.

Add short section to crate docs to mention use of serde_as_consensus
for consensus_encodable types.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI review queuedUpdate API filesby Mitchell Bagot · 76b1f333 · Jul 28, 2026 · 1 fileMessage 28 · OpaqueTriage 0Details
Commit message · Mitchell Bagot

Update API files

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI review queuedconsensus_encoding: Loosen serde_as_consensus trait boundsby Mitchell Bagot · 91a09335 · Jul 28, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Mitchell Bagot

consensus_encoding: Loosen serde_as_consensus trait bounds

The trait bounds in serde_as_consensus currently require Encode + Decode
for either serialize or deserialize. In the case of types which can be
Encoded but not Decoded (e.g. primitives' Block<Checked>) these
over-constrained bounds prevent serde serialisation, or vice-versa.

While this code has been released, removing trait bounds is not breaking
as it loosens the requirements on the type. That is, any Encode + Decode
type is also Encode alone or Decode alone.

Loosen trait bounds in serde_as_consensus to only Encode or Decode as
needed for each function.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
Lower-priorityAdd TapLeafHash to encoding fuzzingby Mitchell Bagot · e15b0ad1 · Jul 28, 2026 · 4 filesMessage 78 · AdequateTriage 5Details
Commit message · Mitchell Bagot

Add TapLeafHash to encoding fuzzing

With the introduction of a new encoding type, the comparison and
roundtrip fuzz targets need to be updated.

Add TapLeafHash to compare_consensus_encoding and encoding roundtrip
fuzz targets.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidence
Security candidatetaproot-primitives: Implement encoding traits for TapLeafHashby Mitchell Bagot · b2ab0896 · Jul 28, 2026 · 2 filesMessage 73 · AdequateTriage 18Details
Commit message · Mitchell Bagot

taproot-primitives: Implement encoding traits for TapLeafHash

The TapLeafHash type in taproot-primitives, is consensus encoded in
PSBT. As such, it needs to have encoding trait implementations.

Add encoder and decoder for TapLeafHash and implement Encode and Decode
on the hash type.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundary
AI review queuedAdd encoding dep to taproot-primitivesby Mitchell Bagot · a291c3a2 · Jul 28, 2026 · 4 filesMessage 68 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Add encoding dep to taproot-primitives

As a first step to introducing encoding for the hash types in
taproot-primitives, the encoding dependency needs to be added to the
crate.

Add consensus_encoding dependency to taproot-primitives.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
Lower-prioritybitcoin: Extern taproot-primitives crateby Mitchell Bagot · 5eb8867f · Jul 28, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Mitchell Bagot

bitcoin: Extern taproot-primitives crate

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd test case for block comparisonby Mitchell Bagot · 458e6b3a · Jul 28, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Add test case for block comparison

To demonstrate the previous patch fix, a new test case that constructs
identical blocks in different manners and compares them should be
included. This both demonstrates the bug, and prevents regressions if
the equivalence logic is changed in the future.

Add block test case that checks equality of identical blocks
constructed in different ways.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
AI review queuedUpdate API filesby Mitchell Bagot · d166d57e · Jul 28, 2026 · 2 filesMessage 28 · OpaqueTriage 0Details
Commit message · Mitchell Bagot

Update API files

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
Lower-priorityReplace Block PartialEq/Eq derive with manual implby Mitchell Bagot · 106563b8 · Jul 28, 2026 · 1 fileMessage 95 · StrongTriage 0Details
Commit message · Mitchell Bagot

Replace Block PartialEq/Eq derive with manual impl

The PartialEq/Eq derive on Block results in incorrect equality
comparisons depending on the method of construction due to the
witness_root cache. Instead, equality for Block should be implemented
manually, comparing the header and transaction lists only.

Replace PartialEq/Eq derive with manual implementations that correctly
compare only the header and transaction lists.
Add test to kill mutants.

95/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
Lower-priorityp2p: Add BIP434 to `NetworkMessage`by rustaceanrob · e1cbf080 · Jul 27, 2026 · 4 filesMessage 76 · AdequateTriage 0Details
Commit message · rustaceanrob

p2p: Add BIP434 to `NetworkMessage`

Adds support for `feature` messages and bumps the protocol version.

ref: https://github.com/bitcoin/bips/blob/master/bip-0434.md

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityp2p: Add BIP434 moduleby rustaceanrob · 622bd341 · Jul 27, 2026 · 2 filesMessage 59 · ThinTriage 0Details
Commit message · rustaceanrob

p2p: Add BIP434 module

This is a new way to advertise support of features without implicit
support via the protocol version.

ref: https://github.com/bitcoin/bips/blob/master/bip-0434.md#feature-message

59/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedbuild(deps): bump github/codeql-action/upload-sarifby dependabot[bot] · 69e50bb3 · Jul 27, 2026 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · dependabot[bot]

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

Bumps [github/codeql-action/upload-sarif](https://github.com/github/codeql-action) from 4.35.5 to 4.36.0.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/github/codeql-action/compare/9e0d7b8d25671d64c341c19c0152d693099fb5ba...7211b7c8077ea37d8641b6271f6a365a22a5fbfa)

---
updated-dependencies:
- dependency-name: github/codeql-action/upload-sarif
dependency-version: 4.36.0
dependency-type: direct:production
update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI review queuedbuild(deps): bump taiki-e/install-action from 2.79.3 to 2.79.12by dependabot[bot] · d953dccc · Jul 27, 2026 · 2 filesMessage 93 · StrongTriage 0Details
Commit message · dependabot[bot]

build(deps): bump taiki-e/install-action from 2.79.3 to 2.79.12

Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.79.3 to 2.79.12.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/65851e10cd6c377f11a60e600abc07cb08643468...6ed6112eb9893c58dd600eebccdf6e77ab7bfa9c)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
dependency-version: 2.79.12
dependency-type: direct:production
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI review queuedUpdate API filesby Mitchell Bagot · a487f942 · Jul 27, 2026 · 3 filesMessage 28 · OpaqueTriage 0Details
Commit message · Mitchell Bagot

Update API files

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
Lower-priorityAdd Hash derive to Opcodeby Mitchell Bagot · 58e13052 · Jul 27, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Mitchell Bagot

Add Hash derive to Opcode

The Opcode type implements all of the common traits except for Display,
Ord and PartialOrd. The Ord traits are excluded due to no natural
ordering and Display due to the current instability in the display
format. However Hash has no such restrictions and should be included.

Add Hash derive to Opcode.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-priorityAdjust test to cover WitnessVersion fmt traitsby Mitchell Bagot · eed88a61 · Jul 27, 2026 · 1 fileMessage 78 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Adjust test to cover WitnessVersion fmt traits

With the new fmt traits on WitnessVersion, tests must be added or
modified to cover the new mutants.

Rename witness_version_display test to witness_version_fmt and include
cases for all format traits.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
AI review queuedUpdate API filesby Mitchell Bagot · 85943c5a · Jul 27, 2026 · 3 filesMessage 28 · OpaqueTriage 0Details
Commit message · Mitchell Bagot

Update API files

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
Lower-priorityAdd fmt traits for WitnessVersionby Mitchell Bagot · 305affb0 · Jul 27, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Mitchell Bagot

Add fmt traits for WitnessVersion

Per the C-NUM-FMT guideline, number types should have Octal, Binary and
Hex formatting. Just as with the block::Version and
transaction::Version types, the WitnessVersion type should also include
these trait impls.
Opcode specifically is excluded as its stringify functionality is still
unclear.

Add {Lower,Upper}Hex, Binary, and Octal trait impls to WitnessVersion.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context