doc: update post-release instructions.
What the developer wrote
Authored by Rusty Russell
doc: update post-release instructions.
Document how to update to the latest bolts, and how to remove deprecated features.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
What changed, and why it matters
This commit only updates the project's internal documentation checklist used after making a software release. It adds instructions for updating version numbers, test files, compatibility tools, and how to remove old deprecated features. There is no code change and no security issue.
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 doc/contribute-to-core-lightning/release-checklist.md, expanding the ‘Post-release’ section with additional maintenance steps: updating Makefile variables (CLN_NEXT_VERSION, CLN_PREV_VERSION), updating downgrade tooling and CI workflow references, syncing BOLT spec revisions, and removing deprecated features two versions after their ‘Last Supported’ release. No source code, build scripts, or CI configurations are actually changed.
Changed components
doc/contribute-to-core-lightning/release-checklist.mdInspect captured patch +7 / −1
diff --git a/doc/contribute-to-core-lightning/release-checklist.md b/doc/contribute-to-core-lightning/release-checklist.md
index 89abf406..42b0ecac 100644
--- a/doc/contribute-to-core-lightning/release-checklist.md
+++ b/doc/contribute-to-core-lightning/release-checklist.md
@@ -99,10 +99,16 @@ Here's a checklist for the release process.
## Post-release
-1. Create a PR to update Makefile's CLN_NEXT_VERSION and important dates for the next release on `.github/PULL_REQUEST_TEMPLATE.md`.
+1. Create a PR to update:
+ * `Makefile`: variables CLN_NEXT_VERSION and CLN_PREV_VERSION (this may break tests as deprecated things are disabled!)
+ * `tools/lightningd-downgrade.c`: to downgrade to the just-released version.
+ * `.github/workflows/ci.yaml`: change old-cln to download the just-released version.
+ * `.github/PULL_REQUEST_TEMPLATE.md` for important dates for the next release.
2. Look through PRs which were delayed for release and merge them.
3. Close out the Milestone for the now-shipped release.
4. Update this file with any missing or changed instructions.
+5. Fetch the latest bolt revision in ../bolts. Then run `./devtools/bolt-catchup.sh` to update BOLTVERSION in the Makefile and run `make check-bolt-quotes`. It may get confused by merges in the BOLTs repository, so you may have to do some manual work. Note: this step may involve a significant amount of work for new spec changes!
+6. Go through `doc/developers-guide/deprecated-features.md` and remove features and code whose `Last Supported` was the prior version (i.e. now two versions ago: we give one version where the user can use `i-promise-to-fix-broken-api-user=FEATURENAME` to re-enable it). Also remove the features from any schemas and other documentation.
## Performing the Point (hotfix) Release
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.