Download Latest Version
wekan-11.72-s390x.zip (286.8 MB)
Get an email when there's a new version of wekan
| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| wekan-10.63-riscv64.zip | 2026-08-04 | 315.7 MB | |
| wekan-10.63-riscv64.zip.sha256sum | 2026-08-04 | 90 Bytes | |
| wekan-10.63-ppc64le.zip | 2026-08-04 | 317.2 MB | |
| wekan-10.63-ppc64le.zip.sha256sum | 2026-08-04 | 90 Bytes | |
| wekan-10.63-sandstorm.spk | 2026-08-04 | 171.2 MB | |
| wekan-10.63-s390x.zip | 2026-08-04 | 318.2 MB | |
| wekan-10.63-s390x.zip.sha256sum | 2026-08-04 | 88 Bytes | |
| wekan-10.63-win64.zip | 2026-08-04 | 297.0 MB | |
| wekan-10.63-win64.zip.sha256sum | 2026-08-04 | 88 Bytes | |
| wekan-10.63-mac-arm64.zip | 2026-08-04 | 307.7 MB | |
| wekan-10.63-mac-arm64.zip.sha256sum | 2026-08-04 | 92 Bytes | |
| README.md | 2026-08-04 | 4.9 kB | |
| v10.63 source code.tar.gz | 2026-08-04 | 34.0 MB | |
| v10.63 source code.zip | 2026-08-04 | 35.3 MB | |
| Totals: 14 Items | 1.8 GB | 0 | |
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.
| Bundle | Binary | From | Version | Checked | SHA256 |
|---|---|---|---|---|---|
| arm64 | FerretDB | wekan/FerretDB | latest | no checksum published | — |
| arm64 | FerretDB | wekan/FerretDB | latest | no checksum published | — |
| arm64 | Node.js | GitHub runner (setup-node) | v22.23.1 | no checksum published | — |
| arm64 | Node.js | GitHub runner (setup-node) | v22.23.1 | no checksum published | — |
| ppc64le | FerretDB | wekan/FerretDB | v1.45.0 | verified | de4518c7774d3025… |
| ppc64le | FerretDB | wekan/FerretDB | v1.45.0 | verified | de4518c7774d3025… |
| ppc64le | Node.js | official | v24.19.0 | verified | c510c6ce12f07010… |
| ppc64le | Node.js | official | v24.19.0 | verified | c510c6ce12f07010… |
| riscv64 | FerretDB | wekan/FerretDB | v1.45.0 | verified | 7dc2952f554e8800… |
| riscv64 | FerretDB | wekan/FerretDB | v1.45.0 | verified | 7dc2952f554e8800… |
| riscv64 | Node.js | unofficial | v24.19.0 | verified | cd1f14af28121480… |
| riscv64 | Node.js | unofficial | v24.19.0 | verified | cd1f14af28121480… |
| s390x | FerretDB | wekan/FerretDB | v1.45.0 | verified | 0ae2e2f2cffdc5dd… |
| s390x | FerretDB | wekan/FerretDB | v1.45.0 | verified | 0ae2e2f2cffdc5dd… |
| s390x | Node.js | official | v24.19.0 | verified | a4792e65962ffa0a… |
| s390x | Node.js | official | v24.19.0 | verified | a4792e65962ffa0a… |
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.
