lint: Temporarily revert to vulture==2.14
What the developer wrote
Authored by MarcoFalke
lint: Temporarily revert to vulture==2.14
To work around https://github.com/bitcoin/bitcoin/issues/34810
What changed, and why it matters
This commit simply pins a Python linting tool (vulture) to an older version in the continuous integration setup. It is a build/maintenance workaround, not a code change affecting Bitcoin Core's runtime behavior, consensus, networking, or wallet security.
No security action required. Treat as routine CI maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff changes one line in ci/lint/01_install.sh, downgrading the vulture dead-code linter from 2.15 to 2.14 to work around an unspecified CI issue (issue #34810). No application code, dependencies consumed by nodes, or cryptographic logic is modified.
Changed components
ci/lint/01_install.shInspect captured patch +1 / −1
diff --git a/ci/lint/01_install.sh b/ci/lint/01_install.sh
index c4429060..4cf695b8 100755
--- a/ci/lint/01_install.sh
+++ b/ci/lint/01_install.sh
@@ -45,7 +45,7 @@ ${CI_RETRY_EXE} pip3 install \
mypy==1.19.1 \
pyzmq==27.1.0 \
ruff==0.15.5 \
- vulture==2.15
+ vulture==2.14
SHELLCHECK_VERSION=v0.11.0
curl -sL "https://github.com/koalaman/shellcheck/releases/download/${SHELLCHECK_VERSION}/shellcheck-${SHELLCHECK_VERSION}.linux.x86_64.tar.xz" | \
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.