Core Lightning

This commit adds a new automated code-quality check that flags risky C functions like gets, scanf, sprintf, fgets, and fputs during pre-commit. It is a defensive tooling change, not a fix for an active security bug. There is no patch to any runtime code, so it does not directly change the software's security posture, but it helps prevent unsafe functions from being introduced in the future.

This commit adds a development tool called shellcheck to the project's pre-commit checks. It is purely a code-quality and linting change; it does not modify any runtime code, fix a bug, or change how the software behaves. There is no security issue in this commit itself.

This commit adds a new developer tool that automatically sorts #include lines in C source files to match the project's coding style. It also wires that tool into the pre-commit checks and removes one stray blank line from a single file. There is no security-relevant code change here.

This commit removes old, deprecated fee-estimate response handling from Core Lightning's Bitcoin backend plugin interface. It was already disabled by default in v24.05 and was scheduled for removal. The change makes the code stricter: if a plugin still returns the old format, Core Lightning will now log an error and stop rather than silently accepting it. This is a cleanup of technical debt, not a fix for an active security vulnerability.

This is a routine post-release maintenance commit for Core Lightning. It updates version numbers in the build files and test infrastructure after a new release, adjusts downgrade tests to reflect that downgrading past the new release no longer fails on a recently-added database feature, and removes some temporary test workarounds for APIs that are no longer considered deprecated. There is no direct security fix here; it is housekeeping that keeps the CI and downgrade tooling aligned with the current release cycle.

This commit simply updates a code comment and developer documentation. It removes an outdated note that said the old way of listing plugin hooks (by name only) should be removed in the future, and instead documents that both the old and new formats are officially supported. There is no security issue here.

This is a small cleanup change that removes an obsolete setting related to announcing websocket addresses. It does not change any security behavior; the feature was already unused.

This is a one-line bug fix in how Core Lightning reads a configuration option named 'i-promise-to-fix-broken-api-user'. The old code expected a simple value, but the actual configuration format stores it as a list of string values. The fix changes the parser to read the list correctly. If left unfixed, the plugin would fail to read the setting and could crash or misbehave when deprecated API behavior is removed, but there is no direct security exploit here.

This commit removes an old, unused function called sign_local_htlc_tx from the wallet's Hardware Security Module (HSM) interface. The function was previously used by the on-chain transaction handler (onchaind) but is no longer called anywhere. The change is a cleanup that also updates a comment about another function used by watchtowers. There is no security fix here.

This commit removes an old, renamed label from the list of features shown for Lightning peers and channels. The old label 'option_anchors_zero_fee_htlc_tx' is replaced by the current spec name 'option_anchors'. It is a routine cleanup of a deprecated JSON-RPC field, not a security fix.

This commit only corrects a typo in the documentation: the planned end-of-life version for a deprecated setting was listed as v26.06, but the actual code uses v26.03. There is no code change and no security impact.

This commit is a trivial Git configuration fix. It updates the .gitattributes file so that a different auto-generated Python file is treated as binary by Git, preventing Git from trying to show text diffs for it. There is no security relevance.

This commit removes the old 'decodepay' JSON-RPC command from Core Lightning. It was already marked as deprecated and users are directed to use the newer 'decode' command instead. There is no security bug being fixed here; it is a routine cleanup of an obsolete API.

This commit removes two old, single-value fields (`tx` and `txid`) from the JSON-RPC and gRPC response of the `close` command. They were already marked as deprecated in version 24.11 and are being replaced by the newer `txs` and `txids` list fields. This is a routine API cleanup, not a security fix.

This commit removes leftover code that tried to read a configuration option called 'max-locktime-blocks' from three payment-related plugins. That option was already removed from the core software, so the code was doing nothing useful. The commit also hardcodes the fallback maximum payment delay to 2016 blocks, which was already the previous default. There is no direct security fix here; it is mostly cleanup of dead code.

This commit updates a GitHub automation script that synchronizes documentation pages with the ReadMe documentation platform. It changes the documentation category slug from 'JSON-RPC API Reference' to 'JSON-RPC' and removes URL-encoding of that slug. It also adds an error message when the ReadMe API request fails. There is no security-relevant change here.

This commit only reformats documentation files and JSON schemas so they display correctly in a new documentation system (MDX). It changes email addresses from angle-bracket style to mailto links, wraps code snippets in backticks, and converts plain URLs to Markdown links. No program code, logic, or security behavior is changed.

This is a routine maintenance update to a GitHub automation script that publishes Core Lightning's RPC documentation to a documentation platform. The script's API call now uses the parameter name 'position' instead of 'order' because the documentation platform changed its API. It also updates the target branch from '1' to 'stable' and improves log messages. There is no security relevance.

This commit only updates documentation build files. It adds a new manual page entry for an existing command (`signmessagewithkey`) and re-sorts some other entries alphabetically. There are no code changes and no security implications.

This is a routine improvement to a GitHub automation script that synchronizes documentation to a third-party service (ReadMe). It adds basic safety checks—verifying an API key is present, confirming files exist before opening them, and switching from document 'title' to 'slug' for matching. There is no indication this fixes a security vulnerability in the Core Lightning software itself; it simply makes a docs-publishing script fail more gracefully and avoid some accidental mismatches or crashes.

This commit only changes how the project's automated testing and build scripts set an environment variable (TEST_LOG_IGNORE_ERRORS=1). It tells the test logging library not to treat certain log-related issues as fatal during test runs. There is no change to the Core Lightning node software, wallet handling, network protocol, cryptography, or any code that runs in production. It is purely a testing-infrastructure convenience fix.

This commit adds a testing-only environment variable that, when enabled, tells Python's logging system not to raise exceptions if something goes wrong while formatting or emitting log messages. It only affects the project's internal Python test harness and has no bearing on real Lightning node operation, funds, network security, or production code.

This commit adds a new data type called 'string_map' to the code generator used for converting between Core Lightning's JSON-RPC interface and its gRPC/Rust interfaces. It is a feature addition for the message generator and testing schema validator, not a security fix or vulnerability patch.

This commit adds a new feature to Core Lightning's REST plugin that lets plugin developers register custom web API paths. It is a feature addition rather than a fix for a known vulnerability. The change expands the attack surface of the REST API by allowing dynamic path registration, but it also includes optional rune-based access controls. There is no direct evidence in the commit of a security bug, though any dynamic routing feature introduces risks if paths are registered carelessly or if input validation is flawed.

This commit simply adds 'Fedora' to the list of Linux distributions whose release binaries are checked against published checksums during the release verification script. It is a build-process expansion, not a code change, and introduces no security vulnerability.