doc: bring lightning-downgrade's version list up to v26.12.
What changed, and why it matters
This commit only updates documentation. It adds new version entries to the manual page for the lightning-downgrade tool and mentions the tool in the upgrade guide. No code, database logic, or security behavior is changed.
No security action needed; this is a routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies two Markdown documentation files. It extends the VERSIONS section of doc/lightning-downgrade.8.md to include v26.04, v26.06, and v26.12 downgrade paths, and updates doc/getting-started/upgrade.md to reference the lightning-downgrade tool. There are no source-code, build, configuration, or cryptographic changes.
Changed components
doc/lightning-downgrade.8.mddoc/getting-started/upgrade.mdInspect captured patch +9 / −1
### 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!)
### 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.Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.