Download Latest Version
wekan-11.72-s390x.zip (286.8 MB)
Get an email when there's a new version of Wekan
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-patches build 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 |
|---|---|---|---|---|---|
| amd64 | FerretDB | wekan/FerretDB | v1.78.0 | verified | 523a96e832e5947a… |
| amd64 | Node.js | nodejs.org | v24.21.0 | verified | fd8e59d5a511510f… |
| arm64 | FerretDB | wekan/FerretDB | v1.78.0 | verified | d8bb85c7ff49fe02… |
| arm64 | Node.js | nodejs.org | v24.21.0 | verified | 6ad1325edbdb5649… |
| armhf | FerretDB | wekan/FerretDB | v1.78.0 | verified | c4df2f4e6fe8fa9a… |
| armhf | Node.js | wekan/node-patches | v24.21.0 | verified | fcd7558bda05a44b… |
| armv6 | FerretDB | wekan/FerretDB | v1.78.0 | verified | eeb962ba8d7b76d7… |
| armv6 | Node.js | wekan/node-patches | v24.21.0 | verified | ea68d25e1eef47cb… |
| armv7 | FerretDB | wekan/FerretDB | v1.78.0 | verified | c4df2f4e6fe8fa9a… |
| armv7 | Node.js | wekan/node-patches | v24.21.0 | verified | 561b357700e2019c… |
| i386 | FerretDB | wekan/FerretDB | v1.78.0 | verified | c855b2f74a7c8b13… |
| i386 | Node.js | wekan/node-patches | v24.21.0 | verified | d3a55c1b0e22c164… |
| mac-arm64 | FerretDB | wekan/FerretDB | v1.78.0 | verified | 34d45b3eee2f322f… |
| mac-arm64 | Node.js | nodejs.org | v24.21.0 | verified | 6239d4cf92d86448… |
| mac-x64 | FerretDB | wekan/FerretDB | v1.78.0 | verified | 1fd4a358aae472d9… |
| mac-x64 | Node.js | nodejs.org | v24.21.0 | verified | 0ae5a24c24bb7d01… |
| ppc64le | FerretDB | wekan/FerretDB | v1.78.0 | verified | ae5e77d7e26ff668… |
| ppc64le | Node.js | nodejs.org | v24.21.0 | verified | 1936fd64623a2f98… |
| riscv64 | FerretDB | wekan/FerretDB | v1.78.0 | verified | c52b5d9b477d8a73… |
| riscv64 | Node.js | unofficial-builds.nodejs.org | v24.21.0 | verified | 5c4e83d46cc1f8ee… |
| s390x | FerretDB | wekan/FerretDB | v1.78.0 | verified | 5f6e44510345e653… |
| s390x | Node.js | nodejs.org | v24.21.0 | verified | 2ef7e2ecbf7a6c2f… |
| win-arm64 | FerretDB | wekan/FerretDB | v1.78.0 | verified | ebd8eb6dac62319d… |
| win-arm64 | Node.js | nodejs.org | v24.21.0 | verified | 8779b1bde1d39f8d… |
| win64 | FerretDB | wekan/FerretDB | v1.78.0 | verified | 39b8bd8b95754497… |
| win64 | Node.js | nodejs.org | v24.21.0 | verified | 158f7685b44de51f… |
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.
v11.66 2026-09-09 WeKan ® release
In short: the companion build repositories under .tools/ move forward:
node-patches gets release-run diagnostics and a real PowerPC startup
check, mongo-tools-patches now tracks upstream master (not a tagged
release) with a Go 1.27 toolchain and expands to forty-three targets
including Android ARM64, and mongosh-patches drops telemetry and fixes
startup in a homeless container user. No WeKan application code changed.
This release updates the following bundled build tooling:
Node.js (node-patches) - release-run diagnostics and a real PowerPC startup check.
Warn when a platform's binary is missing from a completed release run. Thanks to xet7.
A transient runner DNS glitch could fail just the upload step for one platform while its build and checksum succeeded, and the run still finished green with that platform quietly missing from the release. The "attach to the release" step now compares the platforms actually present in `dist/` against the full expected set and emits a `::warning::` naming whatever is missing, pointing at `release-all-missing.yml` to build the gap - instead of requiring someone to notice by comparing sixteen build jobs' logs by hand.Build PowerPC target snapshots and reject Node runtime startup failures. Thanks to xet7.
The released PowerPC binary reported its version but aborted while initializing V8. Real target snapshot tools are now built under QEMU, as for s390x, and both platforms' artifacts are rejected unless JavaScript, separate V8 contexts, crypto and compression actually execute - the gate reproduces the released failure and passes with official same-version Node.MongoDB Database Tools (mongo-tools-patches) - upstream master tracking, Android ARM64, and a wider target matrix.
Build every currently supported native Go target. Thanks to xet7.
Release All expands from seventeen to forty-two OS/CPU targets after compiling current upstream master with Go 1.27 across Go's native command-line platforms, adding AIX, DragonFly BSD, NetBSD, OpenBSD, all FreeBSD CPUs, and Linux MIPS and big-endian PowerPC. Illumos, Solaris and Plan 9 are excluded because current upstream source does not compile there.Add the Android ARM64 command-line target. Thanks to xet7.
The CGO-free upstream tools compile for Android arm64, expanding the canonical registry to forty-three targets and 344 possible binaries. Other Android architectures still require external CGO linking; iOS and WebAssembly do not produce equivalent standalone command-line programs.Allow the expanded tools matrix to finish. Thanks to xet7.
Both full and missing-only workflows now allow three hours for the expanded forty-two target build instead of the former seventeen-target one-hour limit, so adding platforms cannot create a predictably cancelled release.Document that mongo-tools has no telemetry, and pin it against upstream. Thanks to xet7.
Upstream `mongodb/mongo-tools` was checked for an analytics client, a phone-home reporter, or a telemetry/DO_NOT_TRACK flag of its own, the same way wekan/mongosh-patches and this fork's FerretDB were checked before their telemetry was patched out - there is none. `tests/no-telemetry-upstream.sh` re-checks this against the current upstream ref so a future release that adds real telemetry is caught here instead of silently missed.mongosh (mongosh-patches) - telemetry removed, and startup fixed in a homeless container user.
Remove telemetry and fix startup errors in a homeless container user. Thanks to xet7.
The bundled analytics sink is now unconditionally a no-op, so no telemetry HTTP request is ever made regardless of the configured endpoint, and the native machine-id lookup that only existed to key telemetry throttle state is dropped. The startup banner says this fork does not collect or send anything. The same patch fixes mongosh running inside `ghcr.io/wekan/ferretdb` as its default non-root user, which has no `/etc/passwd` entry: config/log/ history storage now falls back to a writable directory under the OS temp dir when the home directory is not writable, instead of failing with `EACCES ... mkdir '/nonexistent'` and "Could not open history file" on every session.Thanks to above GitHub users for their contributions and translators for their translations.
