What the developer wrote
Authored by fanquake
ci: use llvm 22.1.3
What changed, and why it matters
This commit simply updates the version of the LLVM compiler toolchain used in automated testing from 22.1.0 to 22.1.3. It is a routine maintenance change to the project's continuous integration (CI) setup and does not alter Bitcoin Core's actual code or how it runs for users.
No security action needed. Treat as normal dependency/CI maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is a one-line edit in ci/test/01_base_install.sh that changes the git branch/tag used to clone llvm-project when USE_INSTRUMENTED_LIBCPP is set, moving from llvmorg-22.1.0 to llvmorg-22.1.3. This affects only CI builds that instrument the C++ standard library for testing purposes. There is no change to consensus, networking, wallet, or any user-facing code path.
Changed components
ci/test/01_base_install.shInspect captured patch +1 / −1
diff --git a/ci/test/01_base_install.sh b/ci/test/01_base_install.sh
index 5a6e0681..512d1a32 100755
--- a/ci/test/01_base_install.sh
+++ b/ci/test/01_base_install.sh
@@ -62,7 +62,7 @@ if [ -n "$PIP_PACKAGES" ]; then
fi
if [[ -n "${USE_INSTRUMENTED_LIBCPP}" ]]; then
- ${CI_RETRY_EXE} git clone --depth=1 https://github.com/llvm/llvm-project -b "llvmorg-22.1.0" /llvm-project
+ ${CI_RETRY_EXE} git clone --depth=1 https://github.com/llvm/llvm-project -b "llvmorg-22.1.3" /llvm-project
cmake -G Ninja -B /cxx_build/ \
-DLLVM_ENABLE_RUNTIMES="libcxx;libcxxabi;libunwind" \
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.