From 3f652bfd363127e19084612dd269917193f7bfc1 Mon Sep 17 00:00:00 2001 From: Ken Sedgwick Date: Wed, 18 Nov 2026 13:42:44 -0800 Subject: [PATCH 1/2] Makefile: install lightning-downgrade. lightning-downgrade is built with the other tools but is not in BIN_PROGRAMS, so "make install" does not copy it to bindir. The release archives are made from that install, so they have the manual page and not the program: a node upgraded from the release binaries cannot go back without building the tool from source. Add it to BIN_PROGRAMS, next to lightning-hsmtool. Install and uninstall both work from that list. Changelog-Fixed: Tools: `lightning-downgrade` is now installed by `make install` and included in the release archives. Fixes: #9746 --- Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/Makefile b/Makefile index 96495adc1a1f..3aeb0f963210 100644 --- a/Makefile +++ b/Makefile @@ -479,6 +479,7 @@ BIN_PROGRAMS = \ cli/lightning-cli \ lightningd/lightningd \ tools/lightning-hsmtool\ + tools/lightning-downgrade\ tools/reckless PKGLIBEXEC_PROGRAMS = \ lightningd/lightning_channeld \ From 4fcd62584029d355d7dcf72466f3d57167b6bbea Mon Sep 17 00:00:00 2001 From: Ken Sedgwick Date: Wed, 18 Nov 2026 13:45:33 -0800 Subject: [PATCH 2/2] doc: bring lightning-downgrade's version list up to v26.12. The VERSIONS section of lightning-downgrade(8) ended at v25.12. Add v26.04, v26.06 and v26.12. Each goes back one release. The v26.12 tool also removes askrene impressions from the stored layers, because v26.06 cannot read them. The upgrade guide said that downgrades are not generally possible and did not mention the tool. Name it there. Changelog-None --- doc/getting-started/upgrade.md | 2 +- doc/lightning-downgrade.8.md | 8 ++++++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/getting-started/upgrade.md b/doc/getting-started/upgrade.md index 64dca983b1e4..50e32dadb49b 100644 --- a/doc/getting-started/upgrade.md +++ b/doc/getting-started/upgrade.md @@ -10,6 +10,6 @@ Upgrading your Core Lightning node is the same as installing it. So if you previ > 🚧 > -> Upgrades to Core Lightning often change the database: once this is done, downgrades are not generally possible. By default, Core Lightning will exit with an error rather than upgrade, unless this is an official released version. +> Upgrades to Core Lightning often change the database: once this is done, downgrades are not generally possible. The exception is [`lightning-downgrade`](ref:lightning-downgrade), which takes the database of a stopped node back to the previous release (v25.12 and later). By default, Core Lightning will exit with an error rather than upgrade, unless this is an official released version. > > If you really want to upgrade to a non-release version, you can set `database-upgrade=true` in your configuration file, or start `lightningd` with `--database-upgrade=true`(or set to false to never allow a non-reversible upgrade!) diff --git a/doc/lightning-downgrade.8.md b/doc/lightning-downgrade.8.md index dc43492ff0b3..bc40909ce697 100644 --- a/doc/lightning-downgrade.8.md +++ b/doc/lightning-downgrade.8.md @@ -27,6 +27,14 @@ fine with v25.09.1 or v25.09.2, etc. VERSIONS -------- +* *v26.12*: downgrades to v26.06. + + Askrene impressions are removed from the stored layers, because v26.06 cannot read them. + +* *v26.06*: downgrades to v26.04. + +* *v26.04*: downgrades to v25.12. + * *v25.12*: downgrades to v25.09. Downgrade is not possible if `withhold` `true` has been used with `fundchannel_complete`, or if `askrene-bias-node` has been used.