What changed, and why it matters
This commit is a routine build-environment change for Nix development shells. It moves the Python tool `uv` from `buildInputs` to a separate `packages` list in three development shell definitions. There is no indication this change affects Core Lightning's runtime code, network behavior, wallet operations, or any user-facing security property.
No security action required. Review as normal build maintenance if Nix shells are in scope.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch in nix/shells.nix refactors how uv is provided in Nix devShells: pkgs.uv is removed from buildInputs and added to packages in the default, postgres, and rust shells. This is a packaging/dependency-declaration style change for development environments. No source code, cryptographic logic, protocol handling, or configuration defaults are modified.
Changed components
nix/shells.nixInspect captured patch +4 / −4
### nix/shells.nix
@@ -11,10 +11,8 @@
devShells = {
default = pkgs.mkShell {
inputsFrom = [ config.packages.default ];
- buildInputs = [
- pkgs.openssl
- pkgs.uv
- ];
+ buildInputs = [ pkgs.openssl ];
+ packages = [ pkgs.uv ];
# On Linux, uv uses nixpkgs' Python: the Python uv downloads expects
# an FHS dynamic loader, so it doesn't run on NixOS.
# LD_LIBRARY_PATH fixes the following error when running uv pytest tests/:
@@ -28,11 +26,13 @@
postgres = pkgs.mkShell {
inputsFrom = [ config.packages.cln-postgres ];
buildInputs = [ pkgs.openssl ];
+ packages = [ pkgs.uv ];
};
rust = pkgs.craneLib.devShell {
checks = {
inherit (self.checks.${system}) rust;
};
+ packages = [ pkgs.uv ];
};
};
};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.