Download Latest Version wekan-11.72-s390x.zip (286.8 MB)
Email in envelope

Get an email when there's a new version of wekan

Home / v10.77
Name Modified Size InfoDownloads / Week
Parent folder
wekan_10.77_amd64.snap 2026-08-09 397.4 MB
wekan_10.77_arm64.snap 2026-08-09 305.6 MB
wekan-10.77-s390x.zip 2026-08-09 315.6 MB
wekan-10.77-s390x.zip.sha256sum 2026-08-09 88 Bytes
wekan-10.77-ppc64le.zip 2026-08-09 314.8 MB
wekan-10.77-ppc64le.zip.sha256sum 2026-08-09 90 Bytes
wekan-10.77-riscv64.zip 2026-08-09 313.4 MB
wekan-10.77-riscv64.zip.sha256sum 2026-08-09 90 Bytes
wekan-10.77-armv7.zip 2026-08-09 300.4 MB
wekan-10.77-armv7.zip.sha256sum 2026-08-09 88 Bytes
wekan-10.77-armhf.zip 2026-08-09 300.4 MB
wekan-10.77-armhf.zip.sha256sum 2026-08-09 88 Bytes
wekan-10.77-sandstorm.spk 2026-08-09 170.6 MB
wekan-10.77-win64.zip 2026-08-09 294.4 MB
wekan-10.77-win64.zip.sha256sum 2026-08-09 88 Bytes
wekan-10.77-i386.zip 2026-08-09 307.0 MB
wekan-10.77-i386.zip.sha256sum 2026-08-09 87 Bytes
wekan-10.77-mac-arm64.zip 2026-08-09 305.4 MB
wekan-10.77-mac-arm64.zip.sha256sum 2026-08-09 92 Bytes
wekan-10.77-amd64.zip 2026-08-09 306.7 MB
wekan-10.77-amd64.zip.sha256sum 2026-08-09 88 Bytes
wekan-10.77-arm64.zip 2026-08-09 309.6 MB
wekan-10.77-arm64.zip.sha256sum 2026-08-09 88 Bytes
README.md 2026-08-09 14.8 kB
v10.77 source code.tar.gz 2026-08-09 34.3 MB
v10.77 source code.zip 2026-08-09 35.6 MB
Totals: 26 Items   4.0 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 verified 5ae705dd49515a4e…
arm64 FerretDB wekan/FerretDB latest verified 5ae705dd49515a4e…
arm64 Node.js nodejs.org v24.19.0 verified 01443c1e1a29e531…
arm64 Node.js nodejs.org v24.19.0 verified 01443c1e1a29e531…
armhf FerretDB wekan/FerretDB v1.48.0 verified 2232872afa468a83…
armhf FerretDB wekan/FerretDB v1.48.0 verified 2232872afa468a83…
armhf Node.js wekan/node-patches v24.19.0 verified b55350f3071b765a…
armhf Node.js wekan/node-patches v24.19.0 verified b55350f3071b765a…
armv7 FerretDB wekan/FerretDB v1.48.0 verified 2232872afa468a83…
armv7 FerretDB wekan/FerretDB v1.48.0 verified 2232872afa468a83…
armv7 Node.js wekan/node-patches v24.19.0 verified 8dbe0a9aa8550ad5…
armv7 Node.js wekan/node-patches v24.19.0 verified 8dbe0a9aa8550ad5…
i386 FerretDB wekan/FerretDB v1.48.0 verified 63d7a9e5e2754cbf…
i386 FerretDB wekan/FerretDB v1.48.0 verified 63d7a9e5e2754cbf…
i386 Node.js wekan/node-patches v24.19.0 verified 3b0b3bbfe27daf58…
i386 Node.js wekan/node-patches v24.19.0 verified 3b0b3bbfe27daf58…
mac-arm64 FerretDB wekan/FerretDB latest verified 9b15f4c10e473cd0…
mac-arm64 FerretDB wekan/FerretDB latest verified 9b15f4c10e473cd0…
mac-arm64 Node.js nodejs.org v24.19.0 verified 3f1cf157479c1480…
mac-arm64 Node.js nodejs.org v24.19.0 verified 3f1cf157479c1480…
ppc64le FerretDB wekan/FerretDB v1.48.0 verified 0400cd6dfc3d10d9…
ppc64le FerretDB wekan/FerretDB v1.48.0 verified 0400cd6dfc3d10d9…
ppc64le Node.js nodejs.org v24.19.0 verified c510c6ce12f07010…
ppc64le Node.js nodejs.org v24.19.0 verified c510c6ce12f07010…
riscv64 FerretDB wekan/FerretDB v1.48.0 verified d37c35af988670b9…
riscv64 FerretDB wekan/FerretDB v1.48.0 verified d37c35af988670b9…
riscv64 Node.js unofficial-builds.nodejs.org v24.19.0 verified cd1f14af28121480…
riscv64 Node.js unofficial-builds.nodejs.org v24.19.0 verified cd1f14af28121480…
s390x FerretDB wekan/FerretDB v1.48.0 verified 6c7d61fbb8c79b2e…
s390x FerretDB wekan/FerretDB v1.48.0 verified 6c7d61fbb8c79b2e…
s390x Node.js nodejs.org v24.19.0 verified a4792e65962ffa0a…
s390x Node.js nodejs.org v24.19.0 verified a4792e65962ffa0a…
win64 FerretDB wekan/FerretDB latest verified ea57e1bcd153b51d…
win64 FerretDB wekan/FerretDB latest verified ea57e1bcd153b51d…
win64 Node.js nodejs.org v24.19.0 verified 57f71ab3652e797d…
win64 Node.js nodejs.org v24.19.0 verified 57f71ab3652e797d…

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.77 2026-08-09 WeKan ® release

In short: the snap side, which had three problems that looked like one. The helper that put a build on channels released ONE snap, ONE revision, to THREE channels - and a revision number is per architecture, so it could only ever be right for one of them. The page documenting the CPU platforms listed five architectures and omitted armhf, which has been built all along. And the two architectures that are release bundles but NOT snaps - i386 and armv7 - were nowhere, so "missing" and "cannot be there" looked identical. The binaries below are v10.76's: nothing here rebuilds them.

Platform Binary From Version SHA256
amd64 Node.js nodejs.org v24.19.0 14b342e71204f811bde6153be8e04b62aef63c236fef92b55f9c83154b409647
amd64 FerretDB wekan/FerretDB v1.45.0 94713f605167abb45a3717482d35de4824cb4a8f199c1400e826a8a2b04f3893
arm64 Node.js nodejs.org v24.19.0 01443c1e1a29e531ccad5a46fefa6df490d2189c49f7955904aecdbb0fe86fdc
arm64 FerretDB wekan/FerretDB v1.45.0 275ae50ac97e6a70eee72e6de37766c458775c5997c896352db5189c6cf1f04b
loong64 Node.js unofficial-builds.nodejs.org v24.19.0 c24f224726f2d785bd18a1fd09f5e6d1fecf0269928451a60c5da9eac8e92e68
loong64 FerretDB wekan/FerretDB v1.45.0 28bf67981168dfc4bd67698b41dd62628aafe347a77f2b1e6ffcadf009d575e0
mac-arm64 Node.js nodejs.org v24.19.0 3f1cf157479c1480352083105e13faf9d008ede98e7e157746b6df940d197b94
mac-arm64 FerretDB wekan/FerretDB v1.45.0 639ed58b84820b3d588f4161c64d0ab940d0cc6e7d022088d60c2b0b97f99f8e
mac-x64 Node.js nodejs.org v24.19.0 d35e95230f46f6f0751df497c56622c6735e05d5e1fb1630996a005b9d328fe4
mac-x64 FerretDB wekan/FerretDB v1.45.0 fd519903f5630e881e38e7c5814f00c0e89ad26f6785f1ddcbab4058356fc9f3
ppc64le Node.js nodejs.org v24.19.0 c510c6ce12f07010f771e6edb22a3fe23f4f2e6f40b1ffd4941aed0646a0d8b3
ppc64le FerretDB wekan/FerretDB v1.45.0 de4518c7774d302533369c477759ddd866785d6741d98d399388eb8de3df175a
riscv64 Node.js unofficial-builds.nodejs.org v24.19.0 cd1f14af2812148002f58b58a5f9af512a50e3b8e8c148e0db44019dcb68edfd
riscv64 FerretDB wekan/FerretDB v1.45.0 7dc2952f554e8800c4029577901999e06e10272da686f7e402177080067028f9
s390x Node.js nodejs.org v24.19.0 a4792e65962ffa0af42627aacf1122a60c3c88dbf4e4184f06820d66f9da8ba4
s390x FerretDB wekan/FerretDB v1.45.0 0ae2e2f2cffdc5dd2ea4f125281a5e12eea216fbe49b5561d9c001700c3fc0c1
win64 Node.js nodejs.org v24.19.0 57f71ab3652e797d84acddc79c81cc9ff1c6ddb2a1974cdb83f00fee9bff4c73
win64 FerretDB wekan/FerretDB v1.45.0 f6337994368a52d011d438c82b914b0cedb3178fd030acac8db3dab8017cee85

This release adds the following new feature:

Snap publishing - getting every snap onto every channel without typing a revision number.

Release every snap, every architecture, to all four channels. Thanks to xet7. The helper this replaces was `snapcraft release wekan $1 edge,beta,candidate`, which is wrong three ways at once. It names only `wekan`, leaving `wekan-ondra` and `wekan-gantt-gpl` to be done by hand. It takes ONE revision number, and revisions are PER ARCHITECTURE - the store shows `wekan` at 3601 on amd64 and 3600 on arm64 for the same 10.76 - so one number can only ever be right for one of them. And it leaves out `stable`, so a build reached three channels of four and somebody had to remember the fourth. `releases/snap-release-all-channels.sh` resolves the revision per (snap, architecture) from the store itself, so no revision number is ever typed, and releases it to all four channels in ONE call - a revision reaches all of them or none. A pair with no revision is reported and skipped rather than failing the run: the three snaps genuinely have different architecture sets today. The mapping is the hazard, and it lives in one place now (`models/lib/snapArchitectures.js`) with both directions tested. `ppc64le` and `ppc64el` ARE the same hardware - the bundles use the kernel's name, the store uses Debian's - and it is the only rename. Nothing warns when the wrong one is used: an unrecognised architecture is simply one the store has never heard of, so it looks like it worked. Pass the version to pin it. Without one the newest revision of each architecture is promoted, and edge is often ahead of stable, so a bare run publishes edge builds to stable users; `--dry-run` prints the plan first.

and improves the following documentation:

Snap CPU platforms - which six, why not the other two, and how the names differ.

Say which six architectures are snaps, and why i386 and armv7 are not. Thanks to xet7. `docs/Platforms/FOSS/Container/Snap/CPU-platforms.md` listed five architectures and omitted **armhf**, which `snapcraft.yaml` has built all along. It said the release publishes candidate, beta and edge and that stable "is published manually later" - no longer true, and the reason a build reached three channels of four. The matrix is now the six `build-for:` entries with the bundle name beside each, and a new section explains the three ways the two naming systems differ. **armhf and armv7 are not a rename**, and getting it wrong ships a snap that crashes. [node-patches](https://github.com/wekan/node-patches) builds `armhf` to the Debian baseline - hard-float, VFPv3-D16, assuming no NEON - so it runs on any ARMv7-A, and `armv7` with NEON for boards that have it. The Snap Store has ONE 32-bit ARM architecture serving every such device, so it must carry the BASELINE build: the NEON one would be an illegal instruction on a board without NEON. So armv7 ships as a bundle only, and a test cross-checks that explanation against node-patches' own workflow so it cannot drift from the binaries. **i386 cannot have a new snap at all**, and it is categorically different from a missing Node.js build. node-patches patches SOURCE so a binary can be built; here the BASE SNAP does not exist, because Ubuntu 24.04 has no i386 port - no patch set produces a base Canonical does not publish. The last base with one was `core18`, end-of-life. The store still shows an i386 column for `wekan-ondra` because it keeps whatever was ever uploaded; that revision is `0.X-ci` and nothing can replace it. The page also records what each snap has in the store today and what is still to upload, including the two fossils channel promotion cannot fix - `wekan-ondra`'s armhf at 0.22 and its i386 at 0.X-ci, which have no newer revision to promote.

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

Source: README.md, updated 2026-08-09