Makefile: temporarily disable update-doc-examples in update-versions.
What changed, and why it matters
This commit simply removes one build step (update-doc-examples) from a Makefile target used during release version updates. It is a temporary developer workflow change with no visible security relevance. The author promises to restore the step in the next release.
No security action required. Treat as routine build/maintenance change. Monitor the promised follow-up PR if tracking release tooling completeness.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The Makefile target update-versions previously depended on update-pyln-versions, update-reckless-version, update-dot-version, and update-doc-examples. The commit comments out update-doc-examples with a FIXME note and adds a comment indicating it will be restored later. This affects only the release/version-bumping build process, not runtime code, network behavior, or cryptographic operations.
Changed components
MakefileInspect captured patch +1 / −1
diff --git a/Makefile b/Makefile
index 7fa87ea4..f88b3e7a 100644
--- a/Makefile
+++ b/Makefile
@@ -756,7 +756,7 @@ clean: obsclean
# See doc/contribute-to-core-lightning/contributor-workflow.md
PYLNS=client proto testing
-update-versions: update-pyln-versions update-reckless-version update-dot-version update-doc-examples
+update-versions: update-pyln-versions update-reckless-version update-dot-version # FIXME: update-doc-examples
@uv lock
update-pyln-versions: $(PYLNS:%=update-pyln-version-%)
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.