What the developer wrote
Authored by ShahanaFarooqui
ci: Increase timeout
Increased it to 120 since prebuild check is taking 97 minutes locally.
What changed, and why it matters
This commit only changes a GitHub Actions CI workflow setting, increasing the maximum allowed runtime for automated pre-build checks from 30 minutes to 120 minutes. It does not modify any wallet, network, or cryptographic code, and has no direct security relevance to the Lightning node software itself.
No security action needed. This is a benign CI configuration change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates .github/workflows/ci.yaml, changing the timeout-minutes value for the ‘prebuild’ job from 30 to 120. The commit message explains the change is needed because the pre-build check takes about 97 minutes locally. No source code, tests, dependencies, or permissions are altered.
Changed components
.github/workflows/ci.yamlInspect captured patch +1 / −1
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
index cc86761a..ea79a16d 100644
--- a/.github/workflows/ci.yaml
+++ b/.github/workflows/ci.yaml
@@ -22,7 +22,7 @@ jobs:
prebuild:
name: Pre-build checks
runs-on: ubuntu-24.04
- timeout-minutes: 30
+ timeout-minutes: 120
if: |
github.event.action != 'edited' ||
contains(github.event.pull_request.body, 'Changelog')
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.