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.

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.71 2026-08-06 WeKan ® release

In short: the bundled MongoDB Database Tools - bsondump, mongodump, mongoexport, mongofiles, mongoimport, mongorestore, mongostat and mongotop - now come from wekan/mongo-tools-patches instead of the wekan/mongo-tools fork, in every place that downloads them: the amd64 base bundle, the per-arch overwrite in each Linux bundle, the Windows and macOS bundles, the preflight and download checks, the Dockerfile, both snapcraft files, the Flatpak and AppImage workflows and the docs. The fork changed none of upstream's Go source and existed only to carry a build; the new repository keeps that build, clones the newest upstream release and applies patches to it, exactly as wekan/node-patches replaced the wekan/node fork. Nothing about the bundles changes - the same asset names, the same per-tool tolerance for an architecture with no binary, the same checksum verification - and the new checkout beside the repository is excluded from git and from Meteor's file scan like its siblings. Below that: the release scripts now run on the bash 3.2 that macOS ships, so a release can be triggered from a Mac.

This release changes where the bundled MongoDB Database Tools come from:

and has the following developer-tooling changes:

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