AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

Pin backtrace to 0.3.76 for rustc 1.82 through 1.87

Public commit record

What the developer wrote

Authored by auto-pr-bot

91/100 · Strong
Pin backtrace to 0.3.76 for rustc 1.82 through 1.87

@matt asked in issue #5413:

> @auto-pr-bot please add appropriate CI pins to fix the new CI breakage
> like this:
>
> ```
> cargo test -p lightning --quiet --color always --features backtrace
> error: rustc 1.85.1 is not supported by the following packages:
> addr2line@0.27.1 requires rustc 1.88
> backtrace@0.3.77 requires rustc 1.88.0
> gimli@0.34.0 requires rustc 1.88
> Either upgrade rustc or select compatible dependency versions with
> cargo update <name>@<current-ver> --precise <compatible-ver>
> where <compatible-ver> is the latest version supporting rustc 1.85.1
> ```

backtrace v0.3.77 raised its MSRV to 1.88, dragging addr2line 0.27 and
gimli 0.34, which also require rustc 1.88, into the resolution of our
`backtrace` feature. Pinning backtrace to 0.3.76 downgrades those
transitively to 0.25.1 and 0.32.3, which still support our 1.85 MSRV.

The new pin only applies from rustc 1.82, backtrace 0.3.76's own MSRV,
so the existing 0.3.74 pin still covers the 1.75 fuzz-sanity job, and it
stops applying once rustc reaches 1.88.

Fixes #5413

Requested-by: @matt
Link: https://git.rust-bitcoin.org/lightningdevkit/rust-lightning/issues/5413
Authored-By: matt/GLM-5.3-Flash-GGUF:Q4_K_XL <goose@users.noreply.local>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This is a routine build-maintenance change, not a security fix. A newer version of a Rust dependency called 'backtrace' started requiring a newer Rust compiler than the project officially supports, which broke automated tests. The commit pins that dependency to an older compatible version so the test suite can run again. It does not change any code that handles money, network messages, or cryptography.

Recommended action

No security action needed. Treat as normal CI/build maintenance.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.