What changed, and why it matters
This is a build-maintenance patch. It adds one command (`uv lock`) to the Makefile's version-update target so that Python dependency lock files are refreshed after version numbers are changed. There is no security relevance in the commit itself.
No security action required. Treat as routine build tooling maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds @uv lock as a dependency step in the update-versions Makefile target. uv lock regenerates the uv.lock file based on updated Python package versions. This ensures the lockfile stays consistent with the newly bumped versions produced by the other update targets. It is a tooling/CI hygiene change, not a code change to Core Lightning’s runtime, wallet, or network logic.
Changed components
MakefileInspect captured patch +1 / −0
diff --git a/Makefile b/Makefile
index eadb9347..c1c027ae 100644
--- a/Makefile
+++ b/Makefile
@@ -757,6 +757,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
+ @uv lock
update-pyln-versions: $(PYLNS:%=update-pyln-version-%)
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.