-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Release Checklist
Janek Bevendorff edited this page Jan 17, 2026
·
42 revisions
This is a checklist of all the steps to perform for building and publishing a release.
- Backport all pending changes to the
release/2.{MAJOR_VERSION}.xbranch. - Update version number in
CMakeLists.txtandvcpkg.json. - Update
CHANGELOG.md. - Add new version to
share/linux/org.keepassxc.KeePassXC.appdata.xmland copy changelog as XML list. - Add output of
./release-tool.py i18n tx-list-translatorstosrc/gui/AboutDialog.cppand commit the changes. - Update list of (VIP) Patreon supporters and GitHub sponsors to
src/gui/AboutDialog.cppand commit the changes. - Run
./release-tool check {VERSION}and fix any reported errors. - Pull and commit translations with
./release-tool.py i18n tx-pull --commit. - Tag the new release with
./release-tool.py tag {VERSION}and push tags as instructed.
- AppImage: Pull current CI build image with
docker pull ghcr.io/keepassxreboot/keepassxc-ci-docker:focal-qt5.15. - Build binaries with
./release-tool build {VERSION}(AppImage: Use build image with-d). - Build source bundle with
./release-tool build-src {VERSION}.
- Test install/run the built binaries (main and CLI).
- Check settings dialog and passphrase generator for correct bundling of translations and word lists.
- Windows: Check correct bundling of all DLLs.
- AppImage: Check existence of Auto-Type tab on X11.
- Check binaries and src bundle with VirusTotal.
- Sign binaries and src bundle with
./release-tool gpgsign {FILES...}. - Upload src bundle, binaries, and signatures/digests to GitHub.
- Submit Ubuntu PPA builds.
- Submit Flatpak and Snap builds.
- Publish blog post.
Copyright (C) 2016-2026 KeePassXC Team