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.75.0 | verified | 81f6c2ceecae2c7d… |
| amd64 | Node.js | nodejs.org | v24.20.0 | verified | 2f2c0da162318f0d… |
| arm64 | FerretDB | wekan/FerretDB | v1.75.0 | verified | 6eb72515879dd9de… |
| arm64 | Node.js | nodejs.org | v24.20.0 | verified | 5f4ddab610c1ab20… |
| armhf | FerretDB | wekan/FerretDB | v1.75.0 | verified | 9a1641f5546ed4c0… |
| armhf | Node.js | wekan/node-patches | v24.20.0 | verified | ace678ca4601db06… |
| armv6 | FerretDB | wekan/FerretDB | v1.75.0 | verified | a8d4b2522303b626… |
| armv6 | Node.js | wekan/node-patches | v24.20.0 | verified | e01021ab2ddd42cd… |
| armv7 | FerretDB | wekan/FerretDB | v1.75.0 | verified | 9a1641f5546ed4c0… |
| armv7 | Node.js | wekan/node-patches | v24.20.0 | verified | a227473dc166e862… |
| i386 | FerretDB | wekan/FerretDB | v1.75.0 | verified | cadcd51750a50a87… |
| i386 | Node.js | wekan/node-patches | v24.20.0 | verified | a90b92e80d95c341… |
| mac-arm64 | FerretDB | wekan/FerretDB | v1.75.0 | verified | 81863fce8bf935f7… |
| mac-arm64 | Node.js | nodejs.org | v24.20.0 | verified | b7bf7707070b950b… |
| mac-x64 | FerretDB | wekan/FerretDB | v1.75.0 | verified | 01ba473e0b6bed80… |
| mac-x64 | Node.js | nodejs.org | v24.20.0 | verified | 26fc30891004603d… |
| ppc64le | FerretDB | wekan/FerretDB | v1.75.0 | verified | c6a0a83fdfa0e2c2… |
| ppc64le | Node.js | nodejs.org | v24.20.0 | verified | 341307dcee20d883… |
| riscv64 | FerretDB | wekan/FerretDB | v1.75.0 | verified | a33def38abf341f6… |
| riscv64 | Node.js | unofficial-builds.nodejs.org | v24.20.0 | verified | a149c5bf85f98ff1… |
| s390x | FerretDB | wekan/FerretDB | v1.75.0 | verified | 1cd7433952ad29d0… |
| s390x | Node.js | nodejs.org | v24.20.0 | verified | ca381121cb5a8d38… |
| win-arm64 | FerretDB | wekan/FerretDB | v1.75.0 | verified | 407b547bdfa73116… |
| win-arm64 | Node.js | nodejs.org | v24.20.0 | verified | 31c6799744de8a54… |
| win64 | FerretDB | wekan/FerretDB | v1.75.0 | verified | e02457ad24a6ddc7… |
| win64 | Node.js | nodejs.org | v24.20.0 | verified | 6cac9ffbca8f6a47… |
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.63 2026-09-08 WeKan ® release
In short: releases/release-all.sh no longer skips version numbers: its
version step is now a fixed +1, fixing a bug where a single unpublished,
deleted release heading made the script measure and re-apply the resulting
gap forever, silently skipping v11.57, v11.59 and v11.61 (and, earlier,
v11.33 and v11.54). CHANGELOG.md no longer carries an empty Upcoming
placeholder between releases, and each release's binaries table moves from
right under the summary to its own Binaries in these bundles section at
the end. The Docker Hub/Quay.io registry-overview sync added earlier is
removed again: it needed rights the release credentials do not have, and
the maintainer updates both overviews manually now.
This release fixes the following developer-tooling bug:
releases/release-all.sh - the version-number step between releases.
Stop release-all.sh from inheriting and widening a version-number gap (github.com). Thanks to xet7.
The next release version used to be computed by MEASURING the gap between the two newest `# vNN.MM` headings in CHANGELOG.md and re-applying that same gap, rather than always advancing by one. That is fine as long as every gap between two headings is really 1 - but it is not self-correcting: if a release number was ever prepared and then never published, and its CHANGELOG section was deleted outright instead of renamed back to `# Upcoming WeKan ® release` (the correct recovery for a release that never published, per this script's own header comment), the two headings left behind were 2 apart. The script read that as "the cadence is +2 now", applied +2 to get the next number, and did the same again next time - turning one incident into a permanent, ever-repeating habit of skipping a number. That is exactly how v11.56 -> v11.58 -> v11.60 -> v11.62 happened, silently skipping v11.57, v11.59 and v11.61 (v11.33 and v11.54 were skipped by the same bug earlier). The step is now a fixed +1 with no history lookup, and the other code path (resuming an already-renamed release) now hard-fails instead of printing "proceeding anyway" when the newest heading is not exactly +1 from the previous one, so a future gap is caught before it can be built on rather than silently accepted and repeated. `tests/releaseAllVersionStep.test.cjs` pins the fixed +1 step and the hard failure.and the following developer-tooling changes:
CHANGELOG.md - the empty Upcoming placeholder, and where the binaries table sits.
Stop leaving an empty Upcoming placeholder, move the binaries table to the end. Thanks to xet7.
CHANGELOG.md no longer carries an empty `# Upcoming WeKan ® release` section with an `**In short:** nothing here yet.` placeholder between releases. `release-all.sh` used to auto-create one immediately after renaming a release (via the now-deleted `releases/changelog-open-next.mjs`), so the file always had a section that said nothing until the first real entry replaced it. Add the section yourself, by hand, the moment there is a real entry for it, using the skeleton at `docs/DeveloperDocs/Changelog-Upcoming-Template.md`. What actually prevents an entry from landing inside an already-published release - `tests/changelogEntriesBelongToTheirRelease.test.cjs` asking git which commits a release contains - never depended on the placeholder existing first, so removing it costs nothing. Also reorders each release section: the binaries table used to sit right under the `**In short:**` summary; it now comes LAST, under its own `**Binaries in these bundles:**` label, after every content subsection and right before the closing "Thanks to above GitHub users" line - reference material, not the second thing a reader sees.Remove the Docker Hub/Quay.io registry-overview sync (github.com). Thanks to xet7.
v11.62's `release-all.yml` run had already shown this step to be a liability rather than a convenience: `DOCKERHUB_AUTH`/`QUAY_AUTH` are scoped for `docker login`/image push, and neither registry grants a push-scoped token the rights a repository-description write needs, so the step failed with 403 even though the image itself published fine (fixed to a `::warning::` rather than a job failure in the previous commit, still in this same Upcoming section). The maintainer now updates both registries' overviews by hand, so the step - and its `tests/dockerRegistryOverviewSync.test.cjs` - are removed entirely rather than kept working. The identical step is removed from the companion FerretDB fork's `docker.yml` in the same commit round.Binaries in these bundles:
| Platform | Binary | From | Version | SHA256 |
|---|---|---|---|---|
| amd64 | Node.js | nodejs.org | v24.19.0 | 14b342e71204f811bde6153be8e04b62aef63c236fef92b55f9c83154b409647 |
| amd64 | FerretDB | wekan/FerretDB | v1.53.0 | eae1f0a8f73bfc979738bfff7284d40fd1bc55de2cc56514721fc155c3624f7d |
| arm64 | Node.js | nodejs.org | v24.19.0 | 01443c1e1a29e531ccad5a46fefa6df490d2189c49f7955904aecdbb0fe86fdc |
| arm64 | FerretDB | wekan/FerretDB | v1.53.0 | bdc50caee3ac28495b42d2130b94a042a9dd6d3a38f732cac02b648f36c891da |
| mac-arm64 | Node.js | nodejs.org | v24.19.0 | 3f1cf157479c1480352083105e13faf9d008ede98e7e157746b6df940d197b94 |
| mac-arm64 | FerretDB | wekan/FerretDB | v1.53.0 | cb14ffe93e285903e5a8a9c1821687ddb5b8a979a11c584bf4af534b272c6d3e |
| mac-x64 | Node.js | nodejs.org | v24.19.0 | d35e95230f46f6f0751df497c56622c6735e05d5e1fb1630996a005b9d328fe4 |
| mac-x64 | FerretDB | wekan/FerretDB | v1.53.0 | d97dfa9afa60aa05f25384327de82efe7b71d958ed24c1f66618284294a65cd3 |
