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.61 2026-08-04 WeKan ® release

In short: this release is all release-build fixes. With the release job itself working again (v10.60), the per-platform jobs it feeds surfaced their own breakage: build-win64 ran a bash script under PowerShell, build-mac-arm64 called the Linux-only sha256sum, build-extra-arches never unpacked the bundle it downloaded, and an i386 entry in snapcraft.yaml — which core24 cannot build — was a parse error that failed every snap. The downstream Docker and AppImage jobs, which only wrap an already-published release bundle, now skip gracefully instead of failing when that bundle is not up yet. And a Debian type: base snap is scaffolded so i386 can eventually ship as a snap at all, since core24 has no i386 port.

This release fixes the following release-build issues:

The per-platform release jobs - each broke in its own way once the release job started feeding them again.

The downstream packaging jobs - Docker and AppImage only WRAP a release bundle that another job builds, so they cannot run before it exists.

and scaffolds an i386 snap on a Debian base:

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