CI: re-enable docs examples checks.
What changed, and why it matters
This commit simply turns a disabled GitHub Actions CI job back on. It re-enables automatic checks that update examples in the project's documentation schemas and makes the final documentation build depend on that job completing successfully. There is no code change to the lightning node software itself and no security relevance.
No security action needed. This is a routine CI maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change removes if: false from the update-docs-examples job in .github/workflows/ci.yaml, renames it to remove the ‘(disabled temporarily!)’ note, and adds update-docs-examples to the needs: list of the docs job. This is a CI-only workflow change affecting documentation example generation/validation.
Changed components
.github/workflows/ci.yamlInspect captured patch +2 / −2
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
index f7eeb8cc..33535d5b 100644
--- a/.github/workflows/ci.yaml
+++ b/.github/workflows/ci.yaml
@@ -794,8 +794,7 @@ jobs:
if-no-files-found: ignore
update-docs-examples:
- name: Update examples in doc schemas (disabled temporarily!)
- if: false
+ name: Update examples in doc schemas
runs-on: ubuntu-24.04
timeout-minutes: 30
strategy:
@@ -952,6 +951,7 @@ jobs:
- check-units
- integration-valgrind
- integration-sanitizers
+ - update-docs-examples
- min-btc-support
- check-downgrade
- check-compiled-source
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.