Wekan logo

Wekan

Open source kanban board application built with Meteor

Alternative to: trello


About Versions (218)

v10.63

2026-08-04

Binaries in these bundles

Each bundle carries a Node.js, a FerretDB and the MongoDB Database Tools. Which source has a given CPU varies from release to release - nodejs.org builds some architectures, unofficial-builds others, and the wekan/node fork the ones neither of them does - and not every source publishes a checksum. This is what went into this release, and which downloads were checked against a published SHA256.

BundleBinaryFromVersionCheckedSHA256
arm64FerretDBwekan/FerretDBlatestno checksum published
arm64FerretDBwekan/FerretDBlatestno checksum published
arm64Node.jsGitHub runner (setup-node)v22.23.1no checksum published
arm64Node.jsGitHub runner (setup-node)v22.23.1no checksum published
ppc64leFerretDBwekan/FerretDBv1.45.0verifiedde4518c7774d3025…
ppc64leFerretDBwekan/FerretDBv1.45.0verifiedde4518c7774d3025…
ppc64leNode.jsofficialv24.19.0verifiedc510c6ce12f07010…
ppc64leNode.jsofficialv24.19.0verifiedc510c6ce12f07010…
riscv64FerretDBwekan/FerretDBv1.45.0verified7dc2952f554e8800…
riscv64FerretDBwekan/FerretDBv1.45.0verified7dc2952f554e8800…
riscv64Node.jsunofficialv24.19.0verifiedcd1f14af28121480…
riscv64Node.jsunofficialv24.19.0verifiedcd1f14af28121480…
s390xFerretDBwekan/FerretDBv1.45.0verified0ae2e2f2cffdc5dd…
s390xFerretDBwekan/FerretDBv1.45.0verified0ae2e2f2cffdc5dd…
s390xNode.jsofficialv24.19.0verifieda4792e65962ffa0a…
s390xNode.jsofficialv24.19.0verifieda4792e65962ffa0a…

A row saying no checksum published is not a failed check - it is a source that publishes nothing to check against. Those are the ones worth fixing at the source.

v10.63 2026-08-04 WeKan ® release

In short: this release stops “release all missing” from rebuilding the AppImage and Flatpak every run when they are already published. Their checksum files were named with the extension dropped (WeKan-<v>-<arch>.sha256sum), but the missing-check looks for the name the zip bundles use - the asset name plus .sha256sum (WeKan-<v>-<arch>.AppImage.sha256sum) - so it never found the checksum and counted the package as missing. The checksums now keep their extension, matching the check.

This release fixes the following release-build issue:

"Release all missing" no longer rebuilds the AppImage and Flatpak that are already published. Thanks to xet7.

releases/expected-assets.sh decides a package is present only when its binary AND <asset>.sha256sum are both on the release - the same convention the wekan-<v>-<arch>.zip.sha256sum bundles follow. But AppImage.yml and Flatpak.yml wrote the checksum with the extension DROPPED (WeKan-<v>-<arch>.sha256sum rather than WeKan-<v>-<arch>.AppImage.sha256sum), so the check never matched it and reported the AppImage and Flatpak as missing on every run - rebuilding and re-uploading them even when nothing had changed. The checksum (and md5sum) now keep the .AppImage / .flatpak extension, so the check finds them and only genuinely-missing packages are built. The same fix went to the wekan-ondra and wekan-gantt-gpl forks, which name their assets the same way.

Thanks to above GitHub users for their contributions and translators for their translations.