doki Client changelog and checksums
Every release, out in the open.
Read live from the public release repository: every installer, its checksums and the update files, exactly as published.12 releases published
Latest release
v1.6.1
Published 27 October 2026
doki Client v1.6.1 for Windows and Linux. Windows publisher signing is not yet enabled, so the MSI shows an Unknown Publisher warning; every updater payload is integrity-signed with the doki updater key. Verify SHA256SUMS.txt before installation.
Full notes on GitHubEarlier releases.
Newest first, exactly as the release repository has them.
- v1.6.027 October 2026MSI · AppImage · DEB · RPM
- v1.5.014 October 2026MSI · AppImage · DEB · RPM
- v1.4.011 October 2026MSI · AppImage · DEB · RPM
- v1.3.219 September 2026MSI · AppImage · DEB · RPM
- v1.3.119 September 2026MSI · AppImage · DEB · RPM
- v1.3.017 September 2026MSI · AppImage · DEB · RPM
- v1.2.012 September 2026MSI · AppImage · DEB · RPM
- v1.1.110 September 2026MSI · AppImage · DEB · RPM
- v1.1.08 September 2026MSI · AppImage · DEB · RPM
- v1.0.122 August 2026MSI · AppImage · DEB · RPM
- v1.0.020 August 2026MSI · AppImage · DEB · RPM
How a release is made.
There's no fixed schedule. What's fixed is how a build becomes a release.
How doki keeps you safe- Built on real machines
- Each platform is built on its own GitHub runner, Windows on Windows and Linux on Linux, rather than cross-compiled from one machine.
- Published whole, or not at all
- Every file is staged privately first. The release goes public only once the complete set of packages has been checked, so a release is never half finished.
- Shipped with its checksums
- Each release carries the installers, SHA256SUMS.txt for checking them by hand, and latest.json, which the in-app updater reads.
- Only these are official
- Anything built outside that workflow is a development build. If it didn't come from the release repository, it isn't an official doki.