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.
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
This is a routine code cleanup in a Bitcoin library. It renames a simple data container from KeySource to KeyOrigin and gives it named fields (fingerprint and path) instead of numbered tuple slots (.0 and .1). The serialized format is inte…
This change is a routine internal cleanup: the key_expression crate stops depending directly on the secp256k1 cryptography library and instead uses a re-export provided by another internal crate called crypto. No user-facing behavior, type…
This is a small Cargo.toml fix in a Rust Bitcoin subcrate. When the optional 'serde' feature was enabled on the key_expression crate alone, it did not also enable serde on the network crate. That meant a type called NetworkKind could not b…
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…
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
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
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…
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
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 …
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
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
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…
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…
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…
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…
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…
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…
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
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.
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…
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Security candidateMerge rust-bitcoin/rust-bitcoin#6592: primitives: Update API testby Andrew Poelstra · 0969e567 · Aug 10, 2026 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6592: primitives: Update API test
dec8df68621fab7de6196c10f9324244511fe864 Derive Debug on Decoders struct (Mitchell Bagot) a3817e069687658ca3ff8333fbce888a08fc9cb7 Add Encoder struct (Mitchell Bagot) db25c0849cf09d629cab4ea29b10c4ac0f862c47 Add Copy struct for types with Copy (Mitchell Bagot) 57a2fac7573ab6f4b4b0a2c7614ef45859e09afd Extend Debug, Display and serde assertions (Mitchell Bagot) d12a0235501daca84b6c4e78c7727344771d38e9 Extend structs with new types (Mitchell Bagot) 5cb4b69081880a48599f41601d73bfa7b54006ac Add export tests for opcodes and witness_versions (Mitchell Bagot) 4706c5377403d014887b04ebda2ee233ff8afe2c Split locktime re-export test into absolute and relative (Mitchell Bagot) 1966cd470b989b59d70f7dbd16836ff508597bc8 Add new types to module export tests (Mitchell Bagot)
Pull request description:
The API test is intended to check that types in the crate implement various traits and are available to prevent regressions due to later changes. In practice, it hasn't been kept up to date as additions and changes have been made.
ACKs for top commit: apoelstra: ACK dec8df68621fab7de6196c10f9324244511fe864; successfully ran local tests tcharding: ACK dec8df68621fab7de6196c10f9324244511fe864
✓ 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
access controlmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit only updates an internal test file (primitives/tests/api.rs) that checks whether public types implement expected Rust traits and are exported correctly. It adds coverage for new types introduced in earlier development and reorganizes some existing tests. There is no change to production code, no bug fix, and no security-relevant behavior.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6694: units: Flatten Error Constructorsby Andrew Poelstra · 622ab209 · Aug 8, 2026 · 6 filesMessage 91 · StrongInformational 15Details
Refactor nested error constructors with chained `map_err` transformation, This improves readability by making each error conversion step explicit and easy to reason about. - Patch 1: Allows the `unnecessary_map_on_constructor` lint rule. - Patch 2: Flattens double nested `Err` constructors.
ACKs for top commit: apoelstra: ACK 9c43790cc9628606c25eb6cc4bce1b587b699512; successfully ran local tests; kinda code-churny but definitely an improvement
✓ 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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a code cleanup that rewrites how error values are constructed in the Rust Bitcoin library. It changes nested constructor calls like Err(OuterError(InnerError { ... })) into a flatter style using map_err. There is no functional change to how amounts, locktimes, or hex parsing behave, and no security bug is introduced or fixed.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6678: units: Add `Weight::to_vb_*` functions, deprecating `to_vbytes_*`by Andrew Poelstra · 7f614781 · Aug 7, 2026 · 6 filesMessage 91 · StrongInformational 20Details
c4a5a5e64de86f100008972389a76c3eae2faeae Update API files (Mitchell Bagot) 4af70a4eb6a18f4f6ca27c4ea0898f5c9e4bc363 Replace uses of deprecated methods with Weight::to_vb_* (Mitchell Bagot) 519ba8c8a113e679f00a9669ccec51e5c5ef7b54 units: Add Weight::to_vb_* functions, deprecating to_vbytes_* (Mitchell Bagot)
Pull request description:
The Weight type uses from_vb* as the pattern for constructors, but to_vbytes_* for conversion. FeeRate is consistent with to/from_vb*. Before we go to 1.0, Weight's conversion functions should be renamed to keep everything consistent.
Add Weight::to_vb_{floor,ceil} and deprecate Weight::to_vbytes_{floor,ceil}.
ACKs for top commit: apoelstra: ACK c4a5a5e64de86f100008972389a76c3eae2faeae; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 20/100
This is a routine API cleanup in a Rust Bitcoin library. It adds new method names (to_vb_floor, to_vb_ceil) for converting transaction 'weight' to 'virtual bytes' and marks the old names (to_vbytes_floor, to_vbytes_ceil) as deprecated. The actual math is unchanged, and existing callers are updated to use the new names. There is no security bug or fix here.
1c118339ac3d0d4445d2062d9b54e3dbc482b9af crypto: Bump version to 0.3.0 (Tobin C. Harding) b6d44ee8af9f388fc25989c2e9da73bdcf66fd1d primitives: Bump version to 0.103.1 (Tobin C. Harding) 9516435c7371c22e7a6f02b93f65a7231f41e123 primitives: Depend on encoding 1.1.0 (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 1c118339ac3d0d4445d2062d9b54e3dbc482b9af; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
This commit is a routine release-tracking merge. It only bumps version numbers (bitcoin-crypto to 0.3.0 and bitcoin-primitives to 0.103.1), updates dependency version requirements, refreshes lock files, and adds changelog entries. There are no code changes that fix or introduce security behavior.
AI review queuedUpdate API filesby Mitchell Bagot · a75c53c8 · Aug 6, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Mitchell Bagot
Update API files
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit only updates generated API listing files (text snapshots of public functions) to reflect a newly added public function, `to_consensus_u32`, on the `CompactTarget` type. It does not change any source code, logic, or behavior, and therefore has no security relevance on its own.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6675: units: Remove unnecessary track_callerby Andrew Poelstra · ce894f36 · Aug 6, 2026 · 1 fileMessage 100 · StrongInformational 15Details
a1942b52f5efd29a7ed52fd2e77490c24c1809f2 units: Remove unnecessary track_caller (Tobin C. Harding)
Pull request description:
I audited `units` with Claude to check for missing usage of `track_caller`. None found but bot did uncover two usages that are unnecessary because the functions don't panic.
Remove unnecessary `track_caller` attributes on functions that do not panic.
Part of #5518
ACKs for top commit: apoelstra: ACK a1942b52f5efd29a7ed52fd2e77490c24c1809f2; successfully ran local tests
✓ 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
This commit removes two Rust compiler hints (`#[track_caller]`) from helper functions that simply return a value or call a user-provided fallback. These functions never panic, so the hints were unnecessary and had no security effect. The change is a minor code cleanup with no functional or security impact.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6644: primitives: Add serde impls for `WitnessVersion`by Andrew Poelstra · 4981faa7 · Aug 5, 2026 · 2 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6644: primitives: Add serde impls for `WitnessVersion`
3f4adcb9c64a0165b270d7636d9469c0894a6157 Update API files (Mitchell Bagot) 394a351c38dc0b05ad2cd3a8b23fa8f96a30e65f Add tests to cover new serde traits (Mitchell Bagot) ffbdf5729dc87587782883d1895cb5de4d292240 Add serde impls for WitnessVersion (Mitchell Bagot)
Pull request description:
The WitnessVersion type in primitives should have serde trait impls, per the C-SERDE guideline.
Add serde Serialize and Deserialize impls for WitnessVersion.
Contributes to #6630
ACKs for top commit: tcharding: ACK 3f4adcb9c64a0165b270d7636d9469c0894a6157 apoelstra: ACK 3f4adcb9c64a0165b270d7636d9469c0894a6157; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
This commit adds standard serialization/deserialization support for the WitnessVersion type when the optional serde feature is enabled. It is a routine feature addition with no security relevance visible in the code or commit message.
Lower-priorityMerge rust-bitcoin/rust-bitcoin#6671: units: reword docs from height to count in relative locktimeby Andrew Poelstra · 6ea4ff92 · Aug 5, 2026 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6671: units: reword docs from height to count in relative locktime
8867fe2e37f3fcd9e60a763c5e6911445ccdd13e units: reword docs to block count in relative locktime (satsfy (Renato Britto))
Pull request description:
This is a philosophical PR based on [this comment](https://github.com/rust-bitcoin/rust-bitcoin/issues/3632#issuecomment-5160990873). It rewrites the remaining spots that mention relative locktime docs to say block count instead of block height, because a relative lock counts blocks elapsed since the UTXO was confirmed, it is not a chain height.
The goal is to make locktime usage crystal clear to the user. The wording choice regarding lock times is unfortunate.
ACKs for top commit: apoelstra: ACK 8867fe2e37f3fcd9e60a763c5e6911445ccdd13e; successfully ran local tests tcharding: ACK 8867fe2e37f3fcd9e60a763c5e6911445ccdd13e
✓ 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
AI analysis · Informational 15/100
This commit only changes documentation comments and variable names in the rust-bitcoin library. It rewords references to 'block height' as 'block count' for relative locktime, because a relative locktime measures elapsed blocks since a coin was created, not an absolute position in the blockchain. No code behavior changed, so there is no security impact.
The labeller runs in a separate workflow for security reasons, but this forces the `download-artifact` action to need an explicit token.
Here is a test end to end run on my remote: https://github.com/nyonson/rust-bitcoin/pull/5
ACKs for top commit: apoelstra: ACK 715f2bd62fe093c5a01a28b84cf60a6ada9e9756; successfully ran local tests; sure, whatever satsfy: ACK 715f2bd62fe093c5a01a28b84cf60a6ada9e9756 tcharding: ACK 715f2bd62fe093c5a01a28b84cf60a6ada9e9756
✓ 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
credential or privilege statedocumentation-only discountmerge-commit duplicate discount
AI analysis · Informational 15/100
This is a routine GitHub Actions workflow fix. The change gives the automated PR labeler workflow permission to download artifacts and explicitly tells the GitHub CLI which repository to act on. It does not change the Bitcoin library code, user-facing behavior, or introduce a security vulnerability.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
This commit is a routine version bump for the base58ck crate from 0.4.0 to 0.5.0. It only updates version numbers in package manifests, lock files, and adds a changelog entry. There are no code changes and no security relevance.
Security candidateMerge rust-bitcoin/rust-bitcoin#6440: base58: Introduce `decode_check_to_array` for alloc-less decodingby Andrew Poelstra · c5fd1832 · Aug 5, 2026 · 5 filesMessage 100 · StrongInformational 21Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6440: base58: Introduce `decode_check_to_array` for alloc-less decoding
b0eba4c097ca68da53abbbaf8603a5facd7c82bd Rename Error to DecodeCheckError (Mitchell Bagot) 7e6ab80baf795c9985d63c35d54b622ec59daa0a Add tests for decode_check_to_array (Mitchell Bagot) ae6ea3616fd6de3fb8cd976346d0b5d9a537abc7 base58: Add decode_check_to_array (Mitchell Bagot) 0a70c578514c3ecfedac508045397b627071e265 Split decode into build_base256 (Mitchell Bagot)
Pull request description:
At present, base58 has only encoding functionality in no-alloc builds. In order to allow decoding of known size data from base58 without an allocator, the base58 crate needs a decoder function like hex's decode_to_array. Such a function has more failure modes than the alloc decode_check function, so new error types are required also.
- Patch 1 splits the existing decode function into a private build_base256 function that writes to a provided scratch buffer. - Patch 1 introduces decode_check_to_array function for decoding short (<128 char) base58 strings to byte arrays, and associated error types. - Patch 2 adds tests to cover the new function. - Patch 3 renames Error to DecodeCheckError, retaining a deprecated type alias.
ACKs for top commit: tcharding: ACK b0eba4c097ca68da53abbbaf8603a5facd7c82bd apoelstra: ACK b0eba4c097ca68da53abbbaf8603a5facd7c82bd; successfully ran local tests
✓ 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
This commit is a routine feature addition to the rust-bitcoin base58 crate. It adds a new no-allocator function to decode short base58-check strings into fixed-size byte arrays, and renames the existing error type while keeping a deprecated alias for backward compatibility. The changes are mostly refactoring and API expansion; there is no direct evidence of a security vulnerability being fixed.
Security candidateMerge rust-bitcoin/rust-bitcoin#6646: hashes: add several methods to `Midstate` and release 1.2.0by Andrew Poelstra · 0f68fcb3 · Aug 4, 2026 · 10 filesMessage 93 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6646: hashes: add several methods to `Midstate` and release 1.2.0
8899dfd242cf418ee6ce3f05e5828e8579af9f3c release bitcoin_hashes 1.2.0 (Andrew Poelstra) 44552e3ad3035e1001b665bfd4dd3511042cd1f2 hashes: update API files (Andrew Poelstra) 7d8f06d256152a3de1ec9b54e3dd643271983f0d hashes: add several methods to sha256::Midstate for computing them in const contexts (Andrew Poelstra) dc21841b46abc39c49ed7075131f1ac46416137f hashes: add sha256::Midstate::SHA256_IV constant (Andrew Poelstra)
Pull request description:
Adds a new `Midstate::SHA256_IV` constant which allows you to construct a midstate equivalent to a new empty sha256 engine. Then adds `update` methods to `Midstate` which allow you to "ratchet forward" arbitrary midstates, 64 bytes at a time, by hashing the data. There is one fast method and two slow constfn methods.
The motivation is that in Elements we have many Merkle roots which are computed using sha256 midstates, which is safe to do because we're using domain-separated hashes and because our internal nodes are always hashes of exactly 64 bytes of data, which do not not need any length-suffixing. In rust-simplicity we have several such Merkle root types, many of which have a huge pile of precomputed constants, but whose constructors are forced to be non-`const`, which limits their use in generic contexts.
It's maybe a bit uncouth for me to just add some methods I need and cut a new release in a 1.x crate, but
* we have taken great pains to keep `hashes` out of other crates' public APIs, so its stability is not as paramount as it would be for encoding or units, say * all the new methods (and one constant) are on the `Midstate` type, which is a "don't touch this unless you are a cryptographer" part of the API and already has some ugly methods * the additions seem pretty reasonable to me, assuming you accept that we have a `Midstate` type at all; essentially they generalize the already-existing `hash_tag` method * I am BDFL of this project
ACKs for top commit: tcharding: ACK 8899dfd242cf418ee6ce3f05e5828e8579af9f3c
This commit is a routine feature release for the bitcoin_hashes crate. It adds new public methods and a constant to the SHA-256 Midstate type so developers can compute SHA-256 midstates in const contexts. There is no indication of a security bug, fix, or vulnerability. The change expands the public API surface slightly, which is normal for a library release.
Lower-priorityunits: reword docs to block count in relative locktimeby satsfy (Renato Britto) · 8867fe2e · Aug 4, 2026 · 2 filesMessage 73 · AdequateInformational 15Details
Commit message · satsfy (Renato Britto)
units: reword docs to block count in relative locktime
This commit rewords the remaining spots that mention relative locktime docs to say block count instead of block height.
A relative lock counts blocks elapsed since the UTXO confirmed, it is not a chain height.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100
This commit only rewords documentation comments and variable names in the codebase. It changes references from 'block height' to 'block count' for relative lock times, which is a terminology correction with no functional code changes. There is no security impact.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6667: Make the `WitnessesEncoder` privateby Andrew Poelstra · 07d91f7f · Aug 4, 2026 · 4 filesMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6667: Make the `WitnessesEncoder` private
9c391145fa57dc54e6af1f18758db4e0ba2049de Update the API text files (Tobin C. Harding) b37accc3db1f164a5b3dee7ff6bbd7a2d0af5be4 Make the WitnessesEncoder private (Tobin C. Harding)
Pull request description:
The `WitnessesEncoder` is an auxilary encoder that is used internally within the transaction encoder. It does not need to be public.
Make it private and put the code right below where it is used.
ACKs for top commit: apoelstra: ACK 9c391145fa57dc54e6af1f18758db4e0ba2049de; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit makes a small internal helper type called WitnessesEncoder private. It was previously exported as public API but is only used inside the transaction encoder. The change removes it from the public API surface and moves the code closer to where it is used. There is no security bug being fixed here.
Security candidateci: fix labeller permissionsby Nick Johnson · 715f2bd6 · Aug 4, 2026 · 1 fileMessage 75 · AdequateInformational 12Details
Commit message · Nick Johnson
ci: fix labeller permissions
The labeller runs in a separate workflow for security reasons, but this forces the download-artifact actoin to need an explicit token.
75/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege statedocumentation-only discount
AI analysis · Informational 12/100
This commit adjusts a GitHub Actions workflow that automatically labels pull requests based on CI results. It adds a built-in repository token, tells the artifact download step to merge single-file artifacts, and explicitly sets the repository for command-line GitHub operations. There is no change to the Rust Bitcoin library code that end users or applications depend on.
Lower-priorityMerge rust-bitcoin/rust-bitcoin#6661: units: Remove `From<u16>` from `NumberOfBlocks`by Andrew Poelstra · ed5f1b68 · Aug 4, 2026 · 8 filesMessage 91 · StrongInformational 19Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6661: units: Remove `From<u16>` from `NumberOfBlocks`
6ea25bed2982858815abeb8788f12f342584108b Update API files (Mitchell Bagot) f9b08eb1fb1ec6871d144f16c6fdad3d13d9b552 Remove From<u16> from NumberOfBlocks (Mitchell Bagot)
Pull request description:
The NumberOfBlocks type has a From\<u16> impl on it, which is used to simplify construction of the type in various tests. However, the from_height constructor already takes a u16 and functions identically. Since the NumberOf512Seconds type has no such From impl, it should be removed from this to reduce the API surface and make the two consistent.
Remove From\<u16> impl from NumberOfBlocks.
ACKs for top commit: apoelstra: ACK 6ea25bed2982858815abeb8788f12f342584108b; successfully ran local tests tcharding: ACK 6ea25bed2982858815abeb8788f12f342584108b
✓ 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
AI analysis · Informational 19/100
This is a routine API cleanup, not a security fix. The developers removed a shortcut that let programmers create a 'number of blocks' value directly from any u16 number, replacing it with an existing named constructor called from_height. The behavior of the code is unchanged; only the way callers write it is slightly different. There is no vulnerability here.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6668: Scrub the transaction encoding logicby Andrew Poelstra · c5588ba5 · Aug 4, 2026 · 1 fileMessage 91 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6668: Scrub the transaction encoding logic
80dcef1527479e2e0790bf5995636b7640bb56f8 Scrub the transaction encoding logic (Tobin C. Harding)
Pull request description:
Third time lucky. Layout the encoding code in `transaction` as is now customary. (`Transaction` was done but I missed the others.)
Code move only.
ACKs for top commit: apoelstra: ACK 80dcef1527479e2e0790bf5995636b7640bb56f8; successfully ran local tests
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a pure code reorganization (refactor) in the rust-bitcoin library. It moves transaction encoding and decoding definitions around within a single file so the code follows the project's preferred layout. No logic, behavior, or security properties were changed.
Security candidateMerge rust-bitcoin/rust-bitcoin#6662: build(deps): bump actions/checkout from 6.0.2 to 6.0.3by Andrew Poelstra · f7d364cd · Aug 4, 2026 · 15 filesMessage 96 · StrongInformational 18Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6662: build(deps): bump actions/checkout from 6.0.2 to 6.0.3
ae935faddb52aa66087c2c148c8e33a7aaf1a662 build(deps): bump actions/checkout from 6.0.2 to 6.0.3 (dependabot[bot])
Pull request description:
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 6.0.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/checkout/releases">actions/checkout's releases</a>.</em></p> <blockquote> <h2>v6.0.3</h2> <h2>What's Changed</h2> <ul> <li>Update changelog by <a href="https://github.com/ericsciple"><code>@ericsciple</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2357">actions/checkout#2357</a></li> <li>fix: expand merge commit SHA regex and add SHA-256 test cases by <a href="https://github.com/yaananth"><code>@yaananth</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2414">actions/checkout#2414</a></li> <li>Fix checkout init for SHA-256 repositories by <a href="https://github.com/yaananth"><code>@yaananth</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2439">actions/checkout#2439</a></li> <li>Update changelog for v6.0.3 by <a href="https://github.com/yaananth"><code>@yaananth</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2446">actions/checkout#2446</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/yaananth"><code>@yaananth</code></a> made their first contribution in <a href="https://redirect.github.com/actions/checkout/pull/2414">actions/checkout#2414</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/checkout/compare/v6...v6.0.3">https://github.com/actions/checkout/compare/v6...v6.0.3</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/actions/checkout/blob/main/CHANGELOG.md">actions/checkout's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2>v7.0.1</h2> <ul> <li>Skip running unsafe pr check if input is default by <a href="https://github.com/aiqiaoy"><code>@aiqiaoy</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2518">actions/checkout#2518</a></li> <li>Trim only ascii whitespace for branch by <a href="https://github.com/aiqiaoy"><code>@aiqiaoy</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2521">actions/checkout#2521</a></li> <li>Escape values passed to --unset by <a href="https://github.com/aiqiaoy"><code>@aiqiaoy</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2530">actions/checkout#2530</a></li> <li>Various dependency updates</li> </ul> <h2>v7.0.0</h2> <ul> <li>Block checking out fork PR for pull_request_target and workflow_run by <a href="https://github.com/aiqiaoy"><code>@aiqiaoy</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2454">actions/checkout#2454</a></li> <li>Various dependency updates</li> </ul> <h2>v6.0.3</h2> <ul> <li>Fix checkout init for SHA-256 repositories by <a href="https://github.com/yaananth"><code>@yaananth</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2439">actions/checkout#2439</a></li> <li>fix: expand merge commit SHA regex and add SHA-256 test cases by <a href="https://github.com/yaananth"><code>@yaananth</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2414">actions/checkout#2414</a></li> </ul> <h2>v6.0.2</h2> <ul> <li>Fix tag handling: preserve annotations and explicit fetch-tags by <a href="https://github.com/ericsciple"><code>@ericsciple</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2356">actions/checkout#2356</a></li> </ul> <h2>v6.0.1</h2> <ul> <li>Add worktree support for persist-credentials includeIf by <a href="https://github.com/ericsciple"><code>@ericsciple</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2327">actions/checkout#2327</a></li> </ul> <h2>v6.0.0</h2> <ul> <li>Persist creds to a separate file by <a href="https://github.com/ericsciple"><code>@ericsciple</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2286">actions/checkout#2286</a></li> <li>Update README to include Node.js 24 support details and requirements by <a href="https://github.com/salmanmkc"><code>@salmanmkc</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2248">actions/checkout#2248</a></li> </ul> <h2>v5.0.1</h2> <ul> <li>Port v6 cleanup to v5 by <a href="https://github.com/ericsciple"><code>@ericsciple</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2301">actions/checkout#2301</a></li> </ul> <h2>v5.0.0</h2> <ul> <li>Update actions checkout to use node 24 by <a href="https://github.com/salmanmkc"><code>@salmanmkc</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2226">actions/checkout#2226</a></li> </ul> <h2>v4.3.1</h2> <ul> <li>Port v6 cleanup to v4 by <a href="https://github.com/ericsciple"><code>@ericsciple</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2305">actions/checkout#2305</a></li> </ul> <h2>v4.3.0</h2> <ul> <li>docs: update README.md by <a href="https://github.com/motss"><code>@motss</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1971">actions/checkout#1971</a></li> <li>Add internal repos for checking out multiple repositories by <a href="https://github.com/mouismail"><code>@mouismail</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1977">actions/checkout#1977</a></li> <li>Documentation update - add recommended permissions to Readme by <a href="https://github.com/benwells"><code>@benwells</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2043">actions/checkout#2043</a></li> <li>Adjust positioning of user email note and permissions heading by <a href="https://github.com/joshmgross"><code>@joshmgross</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2044">actions/checkout#2044</a></li> <li>Update README.md by <a href="https://github.com/nebuk89"><code>@nebuk89</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2194">actions/checkout#2194</a></li> <li>Update CODEOWNERS for actions by <a href="https://github.com/TingluoHuang"><code>@TingluoHuang</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2224">actions/checkout#2224</a></li> <li>Update package dependencies by <a href="https://github.com/salmanmkc"><code>@salmanmkc</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/2236">actions/checkout#2236</a></li> </ul> <h2>v4.2.2</h2> <ul> <li><code>url-helper.ts</code> now leverages well-known environment variables by <a href="https://github.com/jww3"><code>@jww3</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1941">actions/checkout#1941</a></li> <li>Expand unit test coverage for <code>isGhes</code> by <a href="https://github.com/jww3"><code>@jww3</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1946">actions/checkout#1946</a></li> </ul> <h2>v4.2.1</h2> <ul> <li>Check out other refs/* by commit if provided, fall back to ref by <a href="https://github.com/orhantoy"><code>@orhantoy</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1924">actions/checkout#1924</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/checkout/commit/df4cb1c069e1874edd31b4311f1884172cec0e10"><code>df4cb1c</code></a> Update changelog for v6.0.3 (<a href="https://redirect.github.com/actions/checkout/issues/2446">#2446</a>)</li> <li><a href="https://github.com/actions/checkout/commit/1cce3390c2bfda521930d01229c073c7ff920824"><code>1cce339</code></a> Fix checkout init for SHA-256 repositories (<a href="https://redirect.github.com/actions/checkout/issues/2439">#2439</a>)</li> <li><a href="https://github.com/actions/checkout/commit/900f2210b1d28bbbd0bd22d17926b9e224e8f231"><code>900f221</code></a> fix: expand merge commit SHA regex and add SHA-256 test cases (<a href="https://redirect.github.com/actions/checkout/issues/2414">#2414</a>)</li> <li><a href="https://github.com/actions/checkout/commit/0c366fd6a839edf440554fa01a7085ccba70ac98"><code>0c366fd</code></a> Update changelog (<a href="https://redirect.github.com/actions/checkout/issues/2357">#2357</a>)</li> <li>See full diff in <a href="https://github.com/actions/checkout/compare/de0fac2e4500dabe0009e67214ff5f5447ce83dd...df4cb1c069e1874edd31b4311f1884172cec0e10">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
ACKs for top commit: apoelstra: ACK ae935faddb52aa66087c2c148c8e33a7aaf1a662; successfully ran local tests satsfy: ACK ae935faddb52aa66087c2c148c8e33a7aaf1a662
✓ 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
credential or privilege stateboot or update pathdocumentation-only discountautomated dependency-update discountmerge-commit duplicate discount
AI analysis · Informational 18/100
This commit is a routine update to the GitHub Actions checkout tool used by the project's automated workflows. It changes the pinned version from 6.0.2 to 6.0.3 across many workflow files. The newer version fixes minor bugs related to SHA-256 repositories and merge-commit handling, but the project does not treat this as a security fix. It is a standard maintenance change with very low direct security risk.
AI review queuedMerge rust-bitcoin/rust-bitcoin#6663: build(deps): bump taiki-e/install-action from 2.79.12 to 2.81.4by Andrew Poelstra · 5c92c0b0 · Aug 4, 2026 · 2 filesMessage 96 · StrongInformational 15Details
Commit message · Andrew Poelstra
Merge rust-bitcoin/rust-bitcoin#6663: build(deps): bump taiki-e/install-action from 2.79.12 to 2.81.4
eb9544f9d07a38d81998e5e1f96faaba43546ca0 build(deps): bump taiki-e/install-action from 2.79.12 to 2.81.4 (dependabot[bot])
Pull request description:
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.79.12 to 2.81.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.81.4</h2> <ul> <li> <p>Update <code>vacuum@latest</code> to 0.28.4.</p> </li> <li> <p>Update <code>typos@latest</code> to 1.47.1.</p> </li> <li> <p>Update <code>syft@latest</code> to 1.45.0.</p> </li> <li> <p>Update <code>cargo-neat@latest</code> to 0.4.0.</p> </li> <li> <p>Update <code>cargo-mutants@latest</code> to 27.1.0.</p> </li> </ul> <h2>2.81.3</h2> <ul> <li> <p>Update <code>vacuum@latest</code> to 0.28.3.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.11.18.</p> </li> <li> <p>Update <code>trivy@latest</code> to 0.71.0.</p> </li> </ul> <h2>2.81.2</h2> <ul> <li> <p>Update <code>mise@latest</code> to 2026.5.18.</p> </li> <li> <p>Update <code>cargo-semver-checks@latest</code> to 0.48.0.</p> </li> </ul> <h2>2.81.1</h2> <ul> <li> <p>Update <code>cargo-no-dev-deps@latest</code> to 0.2.24.</p> </li> <li> <p>Update <code>cargo-hack@latest</code> to 0.6.45.</p> </li> </ul> <h2>2.81.0</h2> <ul> <li> <p>Support <code>convco</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/1831">#1831</a>, thanks <a href="https://github.com/graelo"><code>@graelo</code></a>)</p> </li> <li> <p>Support <code>docgarden</code> (<a href="https://redirect.github.com/taiki-e/install-action/pull/1830">#1830</a>, thanks <a href="https://github.com/jesse-black"><code>@jesse-black</code></a>)</p> </li> <li> <p>Update <code>vacuum@latest</code> to 0.28.0.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.19.1.</p> </li> </ul> <h2>2.80.0</h2> <ul> <li>Support <code>kingfisher</code>. (<a href="https://redirect.github.com/taiki-e/install-action/pull/1874">#1874</a>, thanks <a href="https://github.com/SAY-5"><code>@SAY-5</code></a>)</li> </ul> <h2>2.79.15</h2> <ul> <li> <p>Update <code>typos@latest</code> to 1.47.0.</p> </li> <li> <p>Update <code>wasm-tools@latest</code> to 1.251.0.</p> </li> <li> <p>Update <code>vacuum@latest</code> to 0.27.2.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.11.17.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.1.1.</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.85.7] - 2026-08-02</h2> <ul> <li> <p>Update <code>wasmtime@latest</code> to 47.0.3.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.1.</p> </li> <li> <p>Update <code>rclone@latest</code> to 1.75.0.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 1.110.0.</p> </li> </ul> <h2>[2.85.6] - 2026-08-01</h2> <ul> <li> <p>Update <code>wasm-tools@latest</code> to 1.255.0.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.2.5.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.7.18.</p> </li> <li> <p>Update <code>cargo-neat@latest</code> to 0.5.3.</p> </li> <li> <p>Update <code>cargo-crap@latest</code> to 0.4.0.</p> </li> </ul> <h2>[2.85.5] - 2026-07-30</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.0.</p> </li> <li> <p>Update <code>syft@latest</code> to 1.50.0.</p> </li> <li> <p>Update <code>sccache@latest</code> to 0.17.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.7.16.</p> </li> </ul> <h2>[2.85.4] - 2026-07-29</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.11.33.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.7.15.</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/cde8c9e634f4a17bc06b61413ac0ef75450eac46"><code>cde8c9e</code></a> Release 2.81.4</li> <li><a href="https://github.com/taiki-e/install-action/commit/1e4ec7678aaae334aeea28c8427c4e089bd7ac59"><code>1e4ec76</code></a> ci: Temporarily disable broken opensuse/tumbleweed test</li> <li><a href="https://github.com/taiki-e/install-action/commit/2ba2a47530f71d53918fc583d17d787dec4eb506"><code>2ba2a47</code></a> Update <code>vacuum@latest</code> to 0.28.4</li> <li><a href="https://github.com/taiki-e/install-action/commit/193c1cc963fc6015a43bd656c624759cf2489e6d"><code>193c1cc</code></a> Update uv manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/cb4b3f93f764d4397e62fed744879c14a37e6648"><code>cb4b3f9</code></a> Update <code>typos@latest</code> to 1.47.1</li> <li><a href="https://github.com/taiki-e/install-action/commit/b6e08095932286aa3bc8066c8425cf400f5dad11"><code>b6e0809</code></a> Update <code>syft@latest</code> to 1.45.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/55ff171d0ce18bd578689162cd406f47f234b9db"><code>55ff171</code></a> Update prek manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/4dea5bb80f56642c56e7b47dd897c5ecff469424"><code>4dea5bb</code></a> Update mise manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/3e82d2c35aa3d3b9fa923dd8070290a142e32eb9"><code>3e82d2c</code></a> Update cargo-shear manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/31e07c4d25ffc687960959659c9769d3252c88e1"><code>31e07c4</code></a> Update <code>cargo-neat@latest</code> to 0.4.0</li> <li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/6ed6112eb9893c58dd600eebccdf6e77ab7bfa9c...cde8c9e634f4a17bc06b61413ac0ef75450eac46">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
ACKs for top commit: apoelstra: ACK eb9544f9d07a38d81998e5e1f96faaba43546ca0; successfully ran local tests satsfy: ACK eb9544f9d07a38d81998e5e1f96faaba43546ca0
This is a routine Dependabot update that bumps the version of a third-party GitHub Action used only in automated testing workflows. The change does not touch the project's actual Bitcoin library code, and there is no indication it fixes or introduces a security problem.
Lower-priorityUpdate the API text filesby Tobin C. Harding · 9c391145 · Aug 3, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Tobin C. Harding
Update the API text files
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit only updates two generated API text files that list the public surface of the Rust crate. It removes entries for a `WitnessesEncoder` type, reflecting that the type is no longer part of the public API. There is no source code change, no bug fix, and no security-related content in the commit message or diff.
AI review queuedScrub the transaction encoding logicby Tobin C. Harding · 80dcef15 · Aug 3, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · Tobin C. Harding
Scrub the transaction encoding logic
Third time lucky. Layout the encoding code in `transaction` as is now customary. (`Transaction` was done but I missed the others.)
Code move only.
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
AI analysis · Informational 15/100
This commit is a pure code reorganization: it moves existing transaction encoding and decoding definitions around within a single file so they follow the project's preferred layout. No logic was changed, no security bug was fixed, and no new behavior was introduced.
AI review queuedMake the WitnessesEncoder privateby Tobin C. Harding · b37accc3 · Aug 3, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · Tobin C. Harding
Make the WitnessesEncoder private
The `WitnessesEncoder` is an auxilary encoder that is used internally within the transaction encoder. It does not need to be public.
Make it private and put the code right below where it is used.
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply hides an internal helper type called WitnessesEncoder from public view. It is a routine API-cleanup change with no security relevance visible in the code or commit message.
Lower-priorityrelease bitcoin_hashes 1.2.0by Andrew Poelstra · 8899dfd2 · Aug 3, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Andrew Poelstra
release bitcoin_hashes 1.2.0
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit is a routine version bump for the bitcoin_hashes library from version 1.1.0 to 1.2.0. It only updates lock files, the package version number, and the changelog. There is no code change and no security relevance visible in the commit itself.
AI review queuedbuild(deps): bump astral-sh/setup-uv from 8.1.0 to 8.2.0by dependabot[bot] · 1c438632 · Aug 3, 2026 · 2 filesMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]
build(deps): bump astral-sh/setup-uv from 8.1.0 to 8.2.0
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 8.1.0 to 8.2.0. - [Release notes](https://github.com/astral-sh/setup-uv/releases) - [Commits](https://github.com/astral-sh/setup-uv/compare/08807647e7069bb48b6ef5acd8ec9567f424441b...fac544c07dec837d0ccb6301d7b5580bf5edae39)
✓ 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
This is a routine automated update by Dependabot that changes the pinned version of a GitHub Action used to install the 'uv' Python tool in two workflow files. The new commit hash corresponds to the legitimate 8.2.0 release of astral-sh/setup-uv. There is no indication of malicious code or a security vulnerability in this change.
AI review queuedbuild(deps): bump github/codeql-action/upload-sarifby dependabot[bot] · 5293bee4 · Aug 3, 2026 · 1 fileMessage 93 · StrongInformational 15Details
✓ 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
This is a routine automated update by Dependabot that changes the pinned version of a GitHub-provided security scanning helper used in a workflow. It does not modify the project's actual Bitcoin library code, its cryptographic logic, or any code that end users run. There is no indication this introduces a security issue.