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.

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.94 2026-08-16 WeKan ® release

In short: the Windows bundles are back. v10.93 built them, compiled their native modules, and then threw both away on one line: npm on Windows is npm.cmd, a batch script, and Node applies no PATHEXT when it spawns, so execFileSync('npm', …) in the bundle's security-bump step resolved to nothing and build-win64 and build-win-arm64 died with spawnSync npm ENOENT after all the work was done. npm's own CLI is run with the Node already running now, which needs no PATH lookup and no shell. The Sandstorm .spk also failed, on Sandstorm's 1 GiB uncompressed limit, and it failed silently - no list, no sizes, no .spk to inspect - so the pack step now says where the gigabyte is before it packs.

The table below carries only the four platforms this run recorded a complete, verified provenance for; the release job regenerates it from every build job's provenance.tsv.

This release fixes the following build failures:

The release workflow - the bundles a release is supposed to carry.

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