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 \ 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.