CI: don't use /tmp/old-cln, use a local dir.
What changed, and why it matters
This is a minor GitHub Actions CI workflow change. It switches a temporary directory used during automated testing from a shared system folder (/tmp/old-cln) to a local folder (old-cln) in the CI runner's working directory. There is no security vulnerability or user-facing change.
No action required. This is a benign CI configuration change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies .github/workflows/ci.yaml, changing the directory where a previous Core Lightning release binary is downloaded and unpacked for compatibility/regression testing. The path changes from /tmp/old-cln to a relative old-cln directory. This is a CI hygiene/hardness change, not a security patch.
Changed components
.github/workflows/ci.yamlInspect captured patch +3 / −3
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
index cd57c141..a6e51264 100644
--- a/.github/workflows/ci.yaml
+++ b/.github/workflows/ci.yaml
@@ -334,8 +334,8 @@ jobs:
- name: Fetch and unpack previous CLN
run: |
- mkdir /tmp/old-cln
- cd /tmp/old-cln
+ mkdir old-cln
+ cd old-cln
wget https://github.com/ElementsProject/lightning/releases/download/v25.12/clightning-v25.12-ubuntu-24.04-amd64.tar.xz
tar -xaf clightning-v25.12-ubuntu-24.04-amd64.tar.xz
@@ -354,7 +354,7 @@ jobs:
TEST_NETWORK: ${{ matrix.TEST_NETWORK }}
LIGHTNINGD_POSTGRES_NO_VACUUM: 1
VALGRIND: ${{ matrix.VALGRIND }}
- PREV_LIGHTNINGD: /tmp/old-cln/usr/bin/lightningd
+ PREV_LIGHTNINGD: old-cln/usr/bin/lightningd
PYTEST_OPTS: ${{ env.PYTEST_OPTS_BASE }}
run: |
env
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.