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 | 436db5da28b794ab… |
| arm64 | FerretDB | wekan/FerretDB | latest | verified | 436db5da28b794ab… |
| 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.47.0 | verified | 5d1de10a60b0fe4e… |
| armhf | FerretDB | wekan/FerretDB | v1.47.0 | verified | 5d1de10a60b0fe4e… |
| 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.47.0 | verified | 5d1de10a60b0fe4e… |
| armv7 | FerretDB | wekan/FerretDB | v1.47.0 | verified | 5d1de10a60b0fe4e… |
| 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.47.0 | verified | d04499528de4a577… |
| i386 | FerretDB | wekan/FerretDB | v1.47.0 | verified | d04499528de4a577… |
| 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 | d4786d3c1c32ac6b… |
| mac-arm64 | FerretDB | wekan/FerretDB | latest | verified | d4786d3c1c32ac6b… |
| 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.47.0 | verified | 899846a0ab4ec17b… |
| ppc64le | FerretDB | wekan/FerretDB | v1.47.0 | verified | 899846a0ab4ec17b… |
| 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.47.0 | verified | 08ddaefe1e40dd85… |
| riscv64 | FerretDB | wekan/FerretDB | v1.47.0 | verified | 08ddaefe1e40dd85… |
| 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.47.0 | verified | 3aa8d87111fc462e… |
| s390x | FerretDB | wekan/FerretDB | v1.47.0 | verified | 3aa8d87111fc462e… |
| 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 | 25bc69dfb495e2cd… |
| win64 | FerretDB | wekan/FerretDB | latest | verified | 25bc69dfb495e2cd… |
| 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.75 2026-08-09 WeKan ® release
In short: two things the full test run turned up, one in WeKan and one in
the scripts that run it. A linked-card cache that could not see a card
added after the first time a subscription asked, and the build script parity
guard that was the one red suite - right twice over, because build.bat really
was missing the two entries and the guard really could not tell a shell function
from a script. The binaries below are v10.74'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 fixes the following bug:
The board publication - what a subscriber is sent, and when.
Linked-card ids are no longer cached for the life of a subscription. Thanks to xet7.
The helper the five linked-card cursors share memoized its result per board, to spare them the duplicate queries the five copies of that preamble used to make. That is wrong: `publishComposite` re-runs a child's `find()` when the parent document changes, and a cache living for the whole subscription then serves the ids computed the FIRST time forever - a linked card added later would never be published, and one removed would go on being published. The five cursors each ran these same queries before the helper existed, so computing per call is exactly the cost they always had, and it is correct. The guard that pinned the memoization now pins its absence, with the reason, so the next reader does not put it back.and has the following developer-facing change:
The build scripts - what each menu offers, and what the guard between them compares.
git pull and git push work on Windows too, and the parity guard knows what a function entry is. Thanks to xet7.
The one red suite in the full test run, and it was right twice over. The commit that replaced `Update git` with a `git pull` and a `git push` that finish the job added both to `build.sh`'s menu and left `build.bat` behind, so `build.bat git-pull` answered nothing. It answers to both names now, with its own `:gitpull` / `:gitpush` labels - the ones its interactive menu already used. The guard also had to learn what a `!` entry is. It marks something `build.sh` runs ITSELF rather than by executing a file in `releases/`. Most are raw commands and the `.bat` runs those the same way, so those still compare as before; the exception is an entry naming a `build.sh` FUNCTION, which is shell the `.bat` has no way to call. Comparing those as scripts is what made the suite fail the moment `Update git` was replaced. A function entry is exempt from the script comparison now and checked separately: `build.bat` must implement a label of the same name, so one dropping out of a menu still fails.Thanks to above GitHub users for their contributions and translators for their translations.