Pin jobserver to 0.1.34 on pre-1.85 rustc
What changed, and why it matters
This commit adjusts the project's continuous integration (CI) test script to pin an older version of a build-time helper crate called `jobserver` when using older Rust compilers. It is a build compatibility fix, not a security patch, and does not change any production code that handles payments, networking, or cryptography.
No security action needed. Treat as a routine CI/build maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one line to ci/ci-tests-common.sh that runs cargo update -p jobserver --precise 0.1.34 when RUSTC_MINOR_VERSION is below 85. This prevents CI jobs running on Rust versions earlier than 1.85 from pulling in jobserver 0.1.35+, which requires Rust 1.85. There are no changes to rust-lightning library code, dependency lockfiles shipped to users, or cryptographic logic.
Changed components
ci/ci-tests-common.shInspect captured patch +3 / −0
diff --git a/ci/ci-tests-common.sh b/ci/ci-tests-common.sh
index f5313f7..2d8956a 100755
--- a/ci/ci-tests-common.sh
+++ b/ci/ci-tests-common.sh
@@ -20,4 +20,7 @@ PIN_RELEASE_DEPS # pin the release dependencies in our main workspace
# Starting with version 1.9.0, the `zeroize` crate uses Rust 2024.
[ "$RUSTC_MINOR_VERSION" -lt 85 ] && cargo update -p zeroize --precise "1.8.2" --quiet
+# Starting with version 0.1.35, the `jobserver` crate relies on rustc 1.85.
+[ "$RUSTC_MINOR_VERSION" -lt 85 ] && cargo update -p jobserver --precise "0.1.34" --quiet
+
export RUST_BACKTRACE=1
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.