v10.66
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.
| Bundle | Binary | From | Version | Checked | SHA256 |
|---|---|---|---|---|---|
| arm64 | FerretDB | wekan/FerretDB | latest | verified | 275ae50ac97e6a70… |
| arm64 | FerretDB | wekan/FerretDB | latest | verified | 275ae50ac97e6a70… |
| arm64 | Node.js | nodejs.org | v24.19.0 | verified | 01443c1e1a29e531… |
| arm64 | Node.js | nodejs.org | v24.19.0 | verified | 01443c1e1a29e531… |
| armhf | FerretDB | wekan/FerretDB | v1.45.0 | verified | a31a4dd877ecf5d5… |
| armhf | FerretDB | wekan/FerretDB | v1.45.0 | verified | a31a4dd877ecf5d5… |
| armhf | Node.js | fork | v24.19.0 | verified | 63895e1ed4813c80… |
| armhf | Node.js | fork | v24.19.0 | verified | 63895e1ed4813c80… |
| i386 | FerretDB | wekan/FerretDB | v1.45.0 | verified | a259f7f2603b745d… |
| i386 | FerretDB | wekan/FerretDB | v1.45.0 | verified | a259f7f2603b745d… |
| i386 | Node.js | fork | v24.19.0 | verified | 5a5563d4908368c4… |
| i386 | Node.js | fork | v24.19.0 | verified | 5a5563d4908368c4… |
| mac-arm64 | FerretDB | wekan/FerretDB | latest | verified | 639ed58b84820b3d… |
| mac-arm64 | FerretDB | wekan/FerretDB | latest | verified | 639ed58b84820b3d… |
| mac-arm64 | Node.js | nodejs.org | v24.19.0 | verified | 8294b7aa9b039974… |
| mac-arm64 | Node.js | nodejs.org | v24.19.0 | verified | 8294b7aa9b039974… |
| ppc64le | FerretDB | wekan/FerretDB | v1.45.0 | verified | de4518c7774d3025… |
| ppc64le | FerretDB | wekan/FerretDB | v1.45.0 | verified | de4518c7774d3025… |
| ppc64le | Node.js | official | v24.19.0 | verified | c510c6ce12f07010… |
| ppc64le | Node.js | official | v24.19.0 | verified | c510c6ce12f07010… |
| riscv64 | FerretDB | wekan/FerretDB | v1.45.0 | verified | 7dc2952f554e8800… |
| riscv64 | FerretDB | wekan/FerretDB | v1.45.0 | verified | 7dc2952f554e8800… |
| riscv64 | Node.js | unofficial | v24.19.0 | verified | cd1f14af28121480… |
| riscv64 | Node.js | unofficial | v24.19.0 | verified | cd1f14af28121480… |
| s390x | FerretDB | wekan/FerretDB | v1.45.0 | verified | 0ae2e2f2cffdc5dd… |
| s390x | FerretDB | wekan/FerretDB | v1.45.0 | verified | 0ae2e2f2cffdc5dd… |
| s390x | Node.js | official | v24.19.0 | verified | a4792e65962ffa0a… |
| s390x | Node.js | official | v24.19.0 | verified | a4792e65962ffa0a… |
| win64 | FerretDB | wekan/FerretDB | latest | verified | f6337994368a52d0… |
| win64 | FerretDB | wekan/FerretDB | latest | verified | f6337994368a52d0… |
| win64 | Node.js | nodejs.org | v24.19.0 | verified | 57f71ab3652e797d… |
| win64 | Node.js | nodejs.org | v24.19.0 | verified | 57f71ab3652e797d… |
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.66 2026-08-04 WeKan ® release
In short: with linux/386 gone, the multi-arch Docker image build got
past the base image and then failed inside the Dockerfile on linux/arm/v7
(armv7l) - the Dockerfile installs Node.js from nodejs.org / unofficial-builds,
neither of which ships a Node 24 for armv7l, so its arch case has no arm
branch and the build stopped with "Unsupported architecture: arm". armv7l is
dropped from the image's platform list, joining 386 and loong64: it ships as a
.zip bundle but not as a Docker image.
This release fixes the following release-build issue:
The Docker image drops linux/arm/v7 too, which its Dockerfile has no Node 24 to install for. Thanks to xet7.
Removing linux/386 last release let the multi-arch build get past the
ubuntu:26.04 base, and it then failed inside the Dockerfile's RUN step on
linux/arm/v7: "+ echo Unsupported architecture: arm / + exit 1". Docker's
TARGETARCH for linux/arm/v7 is arm, and the Dockerfile's architecture
case handles only amd64/arm64/ppc64le/s390x/riscv64 - it deliberately has no
arm branch, because it installs Node.js from nodejs.org and
unofficial-builds, and NEITHER ships a Node 24 for armv7l. But linux/arm/v7
was still in the docker buildx --platform list, so the RUN reached the
"Unsupported architecture" guard and the whole build failed. linux/arm/v7 is
removed from the build's --platform list and from the want= list that
verifies the pushed manifest, joining linux/386 and linux/loong64: all three
ship as .zip bundles (armhf's Node.js comes from the wekan/node fork there)
but not as Docker images, because the image sources its Node.js from
nodejs.org/unofficial only. tests/releaseDockerPlatforms.test.cjs pins arm/v7
out of both lists.
Thanks to above GitHub users for their contributions and translators for their
translations.