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.35 2026-08-30 WeKan ® release
In short: The Snap Problems report connects to the database endpoint selected by the running services, including an automatically chosen FerretDB port, while preserving explicitly configured external database URLs. Snap services also recover an abandoned endpoint lock instead of appearing active without starting FerretDB.
| 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 fixes the following bugs:
Snap startup - database services and diagnostics share one live endpoint.
Snap problem reports use the database URL of the running services. Thanks to xet7.
Snap services can select a free FerretDB port when the preferred port 27019 is occupied, but `wekan.problems` continued connecting to the old fixed default and reported `ECONNREFUSED` even while FerretDB and WeKan were active. The command now sources the services' shared startup-network state and passes its resolved `MONGO_URL` to the report. An administrator's explicit external database URL remains authoritative. Positive tests execute the real wrapper with a dynamic port and an external URL; negative coverage prevents the obsolete fixed port from returning to the wrapper.Snap services recover abandoned endpoint locks. Thanks to xet7.
WeKan 11.34 could leave an empty `.startup-network.lock` directory without its endpoint state file when a service stopped between acquiring the lock and the atomic state-file rename. Every later service then waited forever: snap showed the shell wrappers as active, but FerretDB never launched and port 27019 refused connections. New locks record their owner. A dead owner's lock is reclaimed immediately, an older empty lock after a short grace period, and a live owner is never displaced. Waiting for a live owner is bounded and fails explicitly instead of presenting a permanently active service. Executable regressions cover both the exact empty-lock failure and a dead-owner lock.Thanks to above GitHub users for their contributions and translators for their translations.