wekan/mongo-tools was a fork of a large Go project that changed none of its source: its six commits were the build workflow and its changelog, and the 738 directories of upstream Go beside them were kept in a fork only so that workflow had somewhere to live. wekan/mongo-tools-patches keeps the build and drops the fork - it clones the newest upstream mongodb/mongo-tools release, applies the patches in its dist/ (there are none yet, which is the honest state of a fork that changed nothing), cross-compiles the eight tools for sixteen platforms with CGO disabled and publishes the same <tool>-<arch>[.exe] assets with a .sha256sum beside each. It is the same move wekan/node-patches made for the retired wekan/node fork.

So every download URL here moved with it: the amd64 base bundle and the per-arch overwrite in the Linux bundle jobs and in releases/repack-bundle-for-arch.sh, the Windows and macOS bundle jobs, releases/check-arch-binaries.sh, releases/require-binaries.sh, releases/test-download-urls.sh, the Dockerfile, snapcraft.yaml and snapcraft-core26.yaml, the Flatpak and AppImage workflows, the Sandstorm build-deps note and the CPU-platforms documentation.

Nothing else changes. The asset names are the same, the per-tool tolerance for an architecture the tools were not built for is the same, and the checksum verification is the same, because the build script moved across unchanged. What does change is that the next release needs wekan/mongo-tools-patches to have published a release first: its Release All has not run yet, and the amd64 bundle’s download of the eight tools is not tolerant of a missing release.

mongo-tools-patches/ is a separate git repository worked on beside WeKan, like node-patches/, FerretDB/ and the mongo-tools/ clone it replaces. It is in .gitignore so it is not untracked noise in git status, and in .meteorignore so Meteor does not walk it during a build - nothing in WeKan imports it. The guard that checks every git repository cloned in here is excluded from BOTH files covers it now.

releases/release-all.sh and releases/version.sh built arrays with mapfile, a bash 4+ builtin absent from the bash 3.2 that macOS still ships, so ./releases/release-all.sh stopped with mapfile: command not found and could not trigger a release from a Mac - and brew install mapfile finds nothing, because mapfile is a shell builtin, not a program. Each mapfile -t VAR < <(cmd) became the portable read loop VAR=(); while IFS= read -r line; do VAR+=("$line"); done < <(cmd), which builds the same array on bash 3.2 and on the bash 5 the Ubuntu release runner uses. Converted: release-all.sh’s RELEASED version list, and version.sh’s three reads - the Node.js files, the MongoDB files, and the two newest CHANGELOG release lines.