Pin backtrace to 0.3.76 for rustc 1.82 through 1.87
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.
No security action needed. Treat as normal CI/build maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit adds a conditional Cargo dependency pin in ci/ci-tests-common.sh. When the Rust compiler minor version is between 1.82 and 1.87 inclusive, it pins the ‘backtrace’ crate to 0.3.76. This prevents Cargo from selecting backtrace 0.3.77, whose transitive dependencies (addr2line 0.27, gimli 0.34) require Rust 1.88, breaking the project’s declared 1.85 MSRV CI jobs. The existing pin to backtrace 0.3.74 for Rust <1.82 is retained. No application or library source code is modified.
Changed components
ci/ci-tests-common.shInspect captured patch +4 / −0
### ci/ci-tests-common.sh
@@ -17,6 +17,10 @@ function PIN_RELEASE_DEPS {
PIN_RELEASE_DEPS # pin the release dependencies in our main workspace
+# The backtrace v0.3.77 crate relies on rustc 1.88, and, as of v0.3.76, the
+# crate relies on rustc 1.82
+[ "$RUSTC_MINOR_VERSION" -ge 82 ] && [ "$RUSTC_MINOR_VERSION" -lt 88 ] && cargo update -p backtrace --precise "0.3.76" --quiet
+
# The backtrace v0.3.75 crate relies on rustc 1.82
[ "$RUSTC_MINOR_VERSION" -lt 82 ] && cargo update -p backtrace --precise "0.3.74" --quiet
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.