Four independent failures in the v10.60 run, one per job: build-win64’s “Check the binaries” step ran set -euo pipefail under the Windows default shell and PowerShell answered “A parameter cannot be found that matches parameter name ‘euo’” - it now says shell: bash. build-mac-arm64 ran sha256sum, a GNU coreutils name macOS does not have, and died exit 127; shasum -a 256 is the BSD/macOS spelling. build-extra-arches downloaded wekan-<version>-amd64.zip but never unpacked it, so the container mounted an empty /bundle and the native-module rebuild died with ENOENT ... /bundle/programs/server/package.json (exit 254) - it now unzips the bundle like the arm64/win64/mac-arm64 jobs already do. And snapcraft.yaml declared an i386 platform that core24 (Ubuntu 24.04, no i386 port) rejects with “none of these build architectures are supported” - a PARSE error that failed snap-native AND every snap-launchpad arch, not only i386. The i386 platform and its launchpad matrix entry are removed; i386 users are served by the .deb and AppImage.

dockerimage.yml / docker-publish.yml build a Dockerfile that DOWNLOADS the prebuilt wekan-<version>-amd64.zip, and AppImage.yml wraps the per-arch bundle; all of them exited hard when that asset was not on the release - which it was not while the release was still building, or when a run targeted a version whose bundle was not published. Each now checks whether the asset it needs is on the release and SKIPS with a ::notice:: (a green run) when it is not: the docker jobs gate the build on the pinned version’s zip, and AppImage flips its per-arch BUILD_THIS off and treats “no AppImage, and no base bundle either” as nothing-to-do. The release image / AppImages are still built by release-all.yml once the bundles are up; these standalone runs simply stop failing in the meantime.

core24 has no i386 port, so base: core24 cannot build an i386 snap. Debian still ships i386 and is glibc, so - unlike an Alpine/musl base - WeKan’s existing binaries run unchanged, and since the snap only assembles the prebuilt wekan-i386.zip (which already exists), the one missing piece is an i386-capable base. snap-base-debian/ scaffolds wekan-base-debian13 (type: base), a trimmed Debian trixie rootfs, starting with i386 - which builds NATIVELY on an amd64 runner, no qemu or Launchpad. It is isolated from the working core24 snapcraft.yaml and is a documented, UNVERIFIED scaffold: a custom base snap needs a real snapcraft pack + local install + a WeKan snap running on it before CI or the (manual) store review, all of which snap-base-debian/README.md spells out.