Core Lightning

This is a routine internal code cleanup in Core Lightning's LSPS (Lightning Service Provider Specification) plugin. It splits an overloaded interface into smaller, more focused pieces. There is no user-facing behavior change, no bug fix, and no security relevance visible in the commit.

This commit is a straightforward internal code reorganization in the Core Lightning LSPS plugin. It moves the JSON-RPC transport/client code from one module to another and updates import paths. There is no security-relevant change to behavior, no bug fix, and no disclosed vulnerability.

This commit refactors the LSPS (Lightning Service Provider Specification) plugin in Core Lightning to replace a heavier custom-message transport layer with a slimmer one. It removes a 536-line transport module and introduces a simpler hook-based multiplexer. The change is a code-quality/architecture refactor; there is no direct evidence in the commit or supplied references that it fixes a security vulnerability.

This commit is a routine code cleanup in a Core Lightning plugin. It swaps one Rust error-handling library (anyhow) for another (thiserror) in the TLV (type-length-value) parsing module. The actual parsing logic and security checks remain the same; only the way errors are represented and reported is changed. There is no indication this fixes a security bug.

This is a tiny code cleanup in a Lightning plugin. The developer replaced a generic Rust error type with a project-specific error type in two function signatures. There is no functional change visible in the diff, no bug fix, and no security-relevant behavior change.

This commit is a pure code refactor: it moves the LSPS2 data model (request/response types, fee calculation, validation, and tests) from one internal module path to another within the same plugin crate. No functionality, logic, or security behavior changes. It is not a security fix.

This commit adds a new internal helper for the LSPS (Lightning Service Provider Specification) plugin that multiplexes JSON-RPC request/response messages over a generic sender. It is purely a refactor/addition of new code with no obvious security bug, no disclosed vulnerability, and no change to existing behavior that callers rely on.

This commit is a routine code reorganization (refactor) for the LSPS (Lightning Service Provider Specification) plugin in Core Lightning. It splits business logic from Core-Lightning-specific RPC calls by moving RPC implementations into a new 'cln_adapters::rpc' module and separating HTLC handling, service handling, and provider traits. There is no indication of a security fix or vulnerability being patched.

This commit adds a new Rust module that lets the LSPS plugin send custom Lightning messages through Core Lightning's RPC interface. It is a straightforward feature implementation with no obvious security bug. There is no indication in the commit that it fixes a vulnerability or addresses a security issue.

This commit is a routine internal code cleanup (refactor) in the LSPS (Lightning Service Provider Specification) plugin for Core Lightning. It merges two similar message-handling paths into one shared implementation and switches the service-side response path to use the same message-sender component already used elsewhere. There is no indication from the commit itself that this fixes a security bug or introduces a vulnerability.

This is a routine code reorganization. Two numeric constants used by the Lightning Service Provider (LSP) plugin are moved from one Rust source file to another so that third-party plugin code can import them more cleanly. The actual values (feature bit 729 and message type 37913) and how they are used do not change.

This commit adds a new experimental plugin feature for the LSPS2 protocol, which lets a Core Lightning node act as a service provider that opens just-in-time channels for payments. The change is purely additive (about 1,500 lines of new Rust code plus tests) and does not patch any reported vulnerability. There is no vendor statement or external report linking it to a security incident.

This commit is a pure code reorganization: it moves the client transport module from one directory (lsps0) to another (cln_adapters) without changing any behavior. The same code is deleted from one file and added to another, with only import paths updated. There is no security fix or vulnerability introduced.

This is a routine Rust code cleanup in a Core Lightning plugin. It changes several function signatures to accept string and byte references instead of owned values, reducing unnecessary memory copies. There is no security-relevant change visible in the diff.

This is a small internal code cleanup in the experimental LSPS (Lightning Service Provider Specification) plugin. It removes a stored peer/node ID from a transport helper struct and instead passes the peer ID as a function argument when sending messages. There is no user-visible behavior change and no security fix.

This is a routine internal code cleanup in Core Lightning's experimental LSPS plugin. It changes how JSON-RPC messages are passed between components, removing unnecessary string conversions and an Arc wrapper. There is no indication this fixes or introduces a security vulnerability.

This commit is a straightforward internal code cleanup in Core Lightning's LSPS (Lightning Service Provider Specification) plugin. It changes how JSON-RPC responses are handled so that transport/parser problems are kept separate from actual JSON-RPC error responses returned by a remote server. There is no indication this fixes a security bug or introduces a vulnerability; it is a refactoring for better code organization.

This commit is a routine code reorganization in Core Lightning's experimental LSPS plugin. It moves standard JSON-RPC error code constants from one internal Rust module to another and adds a new client-rejected error type. There is no security-relevant behavior change, no bug fix, and no vulnerability patch.

This is a straightforward code reorganization: the developer moved shared data types (like monetary amounts and channel identifiers) from a file called 'primitives.rs' into a file called 'lsps0.rs' because the LSPS0 specification actually defines those types. Other files were updated to import from the new location. No behavior changes, bug fixes, or security fixes are visible in the diff.

This commit adds routine helper functions for packaging and unpackaging LSPS0 protocol messages in a new Core Lightning plugin. It is a small, self-contained code addition with no obvious security bug. The functions validate message headers and return clear errors for malformed input.

This commit is a simple code reorganization: it moves helper functions for checking feature bits from a general 'util.rs' file into a new 'core/features.rs' module. No behavior changes are visible in the diff, and no security fixes or vulnerabilities are introduced.

This commit only changes GitHub Actions CI configuration. It adds steps to upload pytest test result files (report.xml) as build artifacts after tests run, even when tests fail. There is no change to application code, no security fix, and no vulnerability introduced.

This commit is a routine cleanup of the project's automated testing configuration. It replaces a messy string-cleanup trick used to name test output files with a simple numeric group identifier. There is no change to the actual Core Lightning software, user data, or network behavior, and no security relevance.

This is a routine cleanup of the project's automated testing configuration. It renames a shared pytest option variable and removes duplicate option settings from individual test jobs. There is no change to the Core Lightning software itself, its network behavior, or its security.

This commit fixes a GitHub Actions workflow syntax error. It replaces an invalid reference to a workflow-level environment variable inside job-level environment sections with the actual values. There is no security issue here—it's purely a CI configuration bug fix that stops 'Unrecognized named-value: env' errors.