Core Lightning v26.12rc1: a double release after a year of vulnerability fixes
Core Lightning published the first release candidate of v26.12 on 18 November. The notes explain that there was no v26.09: an unusually high number of vulnerability reports came in this year, and the developers used that release slot to fix them and ship the fixes in v26.06.x point releases. Work on master continued, so v26.12 is "effectively a double release" with 832 commits since v26.06, and users upgrading from v26.06.x are asked to read the changelog carefully.
For node operators, pay is on its way out: it will be replaced by xpay in v27.03, and the xpay-handle-pay option is deprecated. listforwards and the forward_event notification gain a failure_reason field explaining why a local forward failed, such as insufficient_outgoing_liquidity or too_many_htlcs. lightning-hsmtool can recover HTLC outputs after channel state loss, bkpr-listbalances no longer brings lightningd down when an account's debits exceed its credits, and two splicing bugs are fixed.
For developers, the gRPC wire format is now frozen - released field numbers and types can no longer change, and CI checks every change against the last release - while the Rust types in cln-rpc now treat schema-required fields as required, so messages from nodes older than v26.06 no longer parse. On the protocol side, option_simple_close arrives as an experimental option, interactive channel negotiation fails if outputs exceed 21 million BTC, and a peer reconnecting to a channel where state was lost now reliably triggers a force-close.

Why it matters
The release tells two stories: a year in which security fixes displaced a whole release, and a project now promising that its gRPC interface will not change under integrators. The second is what downstream wallets can plan around.