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.64.0 | verified | c4f0050e35efde2f… |
| amd64 | Node.js | nodejs.org | v24.20.0 | verified | 2f2c0da162318f0d… |
| arm64 | FerretDB | wekan/FerretDB | v1.64.0 | verified | c8421f8da8aa8b56… |
| arm64 | Node.js | nodejs.org | v24.20.0 | verified | 5f4ddab610c1ab20… |
| armhf | FerretDB | wekan/FerretDB | v1.64.0 | verified | 4105a3f0e8b00034… |
| armhf | Node.js | wekan/node-patches | v24.20.0 | verified | b8ed7065d44f0afe… |
| armv6 | FerretDB | wekan/FerretDB | v1.64.0 | verified | 5408b2cb537a4a16… |
| armv6 | Node.js | wekan/node-patches | v24.20.0 | verified | d5cefa6f8cc4acb1… |
| armv7 | FerretDB | wekan/FerretDB | v1.64.0 | verified | 4105a3f0e8b00034… |
| armv7 | Node.js | wekan/node-patches | v24.20.0 | verified | c04c81e539347f39… |
| i386 | FerretDB | wekan/FerretDB | v1.64.0 | verified | 071f9cf5dc434099… |
| i386 | Node.js | wekan/node-patches | v24.20.0 | verified | bb44927307460dcf… |
| mac-arm64 | FerretDB | wekan/FerretDB | v1.64.0 | verified | efc207de01f71473… |
| mac-arm64 | Node.js | nodejs.org | v24.20.0 | verified | b7bf7707070b950b… |
| mac-x64 | FerretDB | wekan/FerretDB | v1.64.0 | verified | db2f40a55e67b3b4… |
| mac-x64 | Node.js | nodejs.org | v24.20.0 | verified | 26fc30891004603d… |
| ppc64le | FerretDB | wekan/FerretDB | v1.64.0 | verified | bb3ca07db3dc512f… |
| ppc64le | Node.js | nodejs.org | v24.20.0 | verified | 341307dcee20d883… |
| riscv64 | FerretDB | wekan/FerretDB | v1.64.0 | verified | 73c18a88dcf0604c… |
| riscv64 | Node.js | unofficial-builds.nodejs.org | v24.20.0 | verified | a149c5bf85f98ff1… |
| s390x | FerretDB | wekan/FerretDB | v1.64.0 | verified | a082dbe2a6d7dc11… |
| s390x | Node.js | nodejs.org | v24.20.0 | verified | ca381121cb5a8d38… |
| win-arm64 | FerretDB | wekan/FerretDB | v1.64.0 | verified | 65d9935475e71787… |
| win-arm64 | Node.js | nodejs.org | v24.20.0 | verified | 31c6799744de8a54… |
| win64 | FerretDB | wekan/FerretDB | v1.64.0 | verified | 3de41a585b997e30… |
| 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.31 2026-08-30 WeKan ® release
In short: User sessions now survive page refreshes and board-view navigation with the HttpOnly-cookie security model. Admin version checks report the newest published WeKan and FerretDB releases with safe localized failure handling. Packaged WeKan also starts on the current Ethernet or WLAN IPv4 address, preferring port 80 and selecting free web and loopback-only FerretDB ports when not configured; Docker Compose follows the same path.
| 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 |
This release adds the following new feature:
The Version pane reads one published component manifest. Thanks to xet7.
A button above the installed-version table asks the server for the fixed `https://wekan.fi/version.txt` resource, then shows its WeKan, FerretDB, Meteor, Node and NPM lines as escaped text in a `pre` block. Only Global Admins can call the method; a ten-second timeout, five exact labels, strict version grammar and a one-kilobyte limit turn offline, malformed and injected responses into one safe localized failure. The release-all website job and the local release path now generate both that file and the identical install-page block from the release and Dockerfile pins plus the validated FerretDB tag. The [website companion commit](https://github.com/wekan/wekan.fi/commit/9b00669354a64d24a1c88dcf5514bbe096be1ff7) adds the initial files. Unit and negative tests cover parsing, generation and workflow wiring, and the production Meteor build passes.and improves packaged startup:
Packaged startup - automatic endpoints stay consistent everywhere.
Packages advertise a working URL on the current network. Thanks to xet7.
When `ROOT_URL` is not configured, the bundle ZIP, Docker image, AppImage, Windows single executable and Snap now discover the active IPv4 address and a port the runtime can bind. Port 80 is preferred and produces a clean `http://IP-address` URL; another free port is selected and included in the URL when port 80 is unavailable. Bundled FerretDB independently selects a free localhost-only port, and `MONGO_URL` follows that exact endpoint. Startup logs show the resulting `ROOT_URL`, `PORT`, FerretDB address and `MONGO_URL`, while explicit deployment settings remain authoritative. Positive and negative tests cover automatic and configured endpoints, loopback enforcement and all five packaging paths; all 694 Node suites pass.Compose leaves deployment endpoints to automatic startup. Thanks to xet7.
The seven single-instance Docker Compose files no longer activate hard-coded `ROOT_URL`, `PORT` or `MONGO_URL` values. Their commented configuration explains that startup selects the current IPv4 and a usable port, derives the internal MongoDB or FerretDB service URL from Compose metadata, and prints every resolved endpoint in the Node console. Published container port 80 now agrees with the automatic preference. The POSIX and Windows offline launchers document and use the same resolver, and Docker no longer preselects port 27017 before its free localhost-port check. Positive and negative tests cover MongoDB, FerretDB v1, authenticated FerretDB v2, explicit overrides and every configuration file. The private-board refresh browser regression passes with both repo-local FerretDB and Meteor's included MongoDB; all 694 Node suites pass.and fixes the following bug:
Private-board sessions survive page refreshes. Thanks to lucasarrudadev and xet7.
WeKan configured Meteor's HttpOnly-cookie session mode after the Accounts client had already performed its one startup resume check. A successful login wrote the protected cookie, but a fresh page held no token in its intentionally memory-only client storage and never asked the cookie endpoint to restore it. WeKan now starts Meteor's public cookie-login path immediately after enabling the mode, so refreshes and board-view navigations restore the same user instead of showing Sign In. Static positive and negative tests preserve the protected flow, and a Chromium regression reloads a private board against the repo-local Meteor server and included MongoDB and verifies both the user and board remain.and improves the following translations:
Version checking reports failures in the user's language. Thanks to xet7.
The check button and its offline, timeout or invalid-response message now use dedicated translation keys. Every locale keeps the English key order, every previously complete non-English locale has localized text, and only the same 37 already-incomplete locales retain English placeholders. Regression coverage checks all locale files, representative natural translations and the existing placeholder inventory; all 695 plain-Node suites and the production Meteor build pass.Thanks to above GitHub users for their contributions and translators for their translations.