Skip to content

Making Releases

Release checklist

Here's a checklist for the release process.

Leading Up To The Release

  1. Talk to team about whether there are any changes which MUST go in this release which may cause delay.
  2. Look through outstanding issues, to identify any problems that might be necessary to fixup before the release. Good candidates are reports of the project not building on different architectures or crashes.
  3. Identify a good lead for each outstanding issue, and ask them about a fix timeline.
  4. Create a milestone for the next release on Github, and go though open issues and PRs and mark accordingly.
  5. Ask (via email) the most significant contributor who has not already named a release to name the release (use devtools/credit to find this contributor). CC previous namers and team.

Preparing for -rc1

  1. Check that is well formatted, ordered in areas, covers all signficant changes, and sub-ordered approximately by user impact & coolness.
  2. Use devtools/ to collect the changelog entries from pull request commit messages and merge them into the manually maintained This does API queries to GitHub, which are severely ratelimited unless you use an API token: set the GH_TOKEN environment variable to a Personal Access Token from
  3. Create a new heading to v<VERSION>rc1, and create a link at the bottom. Note that you should exactly copy the date and name format from a previous release, as the script relies on this.
  4. Update the contrib/pyln package versions: make update-pyln-versions NEW_VERSION=<VERSION>
  5. Create a PR with the above.

Releasing -rc1

  1. Merge the above PR.
  2. Tag it git pull && git tag -s v<VERSION>rc1. Note that you should get a prompt to give this tag a 'message'. Make sure you fill this in.
  3. Confirm that the tag will show up for builds with git describe
  4. Push the tag to remote git push --tags.
  5. Update the /topic on #c-lightning on Libera.
  6. Prepare draft release notes (see devtools/credit), and share with team for editing.
  7. Upgrade your personal nodes to the rc1, to help testing.
  8. Test tools/ to build the non-reprodicible images and reproducible zipfile.
  9. Use the zipfile to produce a reproducible build.

Releasing -rc2, etc

  1. Change rc1 to rc2 in
  2. Add a PR with the rc2.
  3. Tag it git pull && git tag -s v<VERSION>rc2 && git push --tags
  4. Update the /topic on #c-lightning on Libera.
  5. Upgrade your personal nodes to the rc2.

Tagging the Release

  1. Update the; remove -rcN in both places, update the date and add title and namer.
  2. Add a PR with that release.
  3. Merge the PR, then:
  4. export VERSION=0.9.3
  5. git pull
  6. git tag -a -s v${VERSION} -m v${VERSION}
  7. git push --tags
  8. Run tools/ to build the non-reprodicible images and reproducible zipfile.
  9. Use the zipfile to produce a reproducible build.
  10. Create the checksums for signing: sha256sum release/* > release/SHA256SUMS
  11. Create the first signature with gpg -sb --armor release/SHA256SUMS
  12. Upload the files resulting files to github and save as a draft. (
  13. Ping the rest of the team to check the SHA256SUMS file and have them send their gpg -sb --armor SHA256SUMS.
  14. Append the signatures into a file called SHA256SUMS.asc, verify with gpg --verify SHA256SUMS.asc and include the file in the draft release. 11.make pyln-release to upload pyln modules to

Performing the Release

  1. Edit the GitHub draft and include the SHA256SUMS.asc file.
  2. Publish the release as not a draft.
  3. Update the /topic on #c-lightning on Libera.
  4. Send a mail to c-lightning and lightning-dev mailing lists, using the same wording as the Release Notes in github.


  1. Look through PRs which were delayed for release and merge them.
  2. Close out the Milestone for the now-shipped release.
  3. Update this file with any missing or changed instructions.