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.

v11.29 2026-08-30 WeKan ® release

In short: Release builds now wait for every AppImage input, hand a slow riscv64 Launchpad build off cleanly, and start the Enigma-packaged Windows EXE despite its false legacy-Windows version result. Browser tests follow the new HttpOnly session model, the Helm chart has a viable default memory budget, and AWS storage, PDF generation, browser automation and Playwright's MongoDB driver are updated.

This release updates the following dependencies:

• @aws-sdk/client-s3 3.1117.0 → 3.1119.0 — the Amazon S3 client.
• @aws-sdk/lib-storage 3.1114.0 → 3.1119.0 — managed multipart uploads to S3.
• mongodb 7.5.0 → 7.6.0 — the Playwright test database driver.
• pdfkit 0.19.1 → 0.20.1 — PDF generation.
• puppeteer 25.8.0 → 25.9.0 — browser automation.

Thanks to dependabot.

and fixes the following developer-tooling bugs:

Build and release tooling - every scheduled artifact path completes or hands its remote work off cleanly.

The test harness - authentication and static checks match the production session model and the workflows they validate.

The Helm chart - the default pod budget fits WeKan's container-aware Node.js heap and native processes.

• The default WeKan pod requests 512 MiB with a 2 GiB limit. Thanks to xet7.

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