From 8097a5616d9e9d11a06fdacc6c64781b8050da57 Mon Sep 17 00:00:00 2001 From: Ilker Manap Date: Mon, 28 Sep 2026 11:50:12 +0200 Subject: [PATCH] Describe v0.8.2 Co-Authored-By: Claude Opus 5.5 (1M context) --- CHANGELOG.md | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4a4ba06..b0691af 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -18,6 +18,45 @@ is only released once its **exit criterion** is met, not when its code lands. Until v1.0.0 the minor version is the breaking one: configuration formats and Go APIs change between minors without a deprecation period. +## v0.8.2 — 2026-09-28 + +A node no longer runs whatever engine somebody once put on it. It installs its +own. + +### Engines are installed by the node + +`engines:` in server.yaml names the engines every node has and their versions, +defaulting to the llama.cpp build this release was checked against (b10991). +Each agent converges on it: it picks the build for its hardware — CUDA with its +runtime when an NVIDIA driver is loaded, CPU otherwise — installs the OS +packages that build needs with the machine's own package manager, downloads the +archive and checks it against the sha256 GitHub publishes, unpacks it refusing +anything that would land outside its directory, and runs it. `ldd` names a +missing library or a system too old for the build ("libstdc++.so.6 is too old +(needs GLIBCXX_3.4.30)"); `--version` proves the rest. Installs are checked +again every ten minutes. + +An engine is reported only once installed and seen to run, or when the agent's +configuration names it on purpose. A node that has installed nothing yet is not +a candidate for any model, where before it was a candidate for all of them. +`ctl nodes`, the cluster page and placement's refusals say where each +installation stands, and warn about a CPU without AVX2. + +Not every system is refused for its name: the build runs on Ubuntu 22.04+, +Debian 12+ and RHEL-family 10, and `ldd` decides. vLLM and SGLang are not yet +installed this way and must still be named in the agent's configuration. + +### Onboarding + +Onboarding installs llmgw from the CI release for the node's architecture, +checked against the release's checksums, and writes an agent configuration of +only the control plane's addresses and the TLS files. + +### Fixes + +- A race on the weights fingerprint, which two heartbeat loops touched during a + failover. + ## v0.8.1 — 2026-09-28 Nothing here changes a configuration format: every file that worked with