Diluvium 5.5.1_build9

[5.5.1_build9] - 2026-08-15

v5.5.1_build9 · Lua 5.5.1 · bytecode format 0x46

The host ships. Build 8 added a plugin channel and a generic host
that could defer a call, and published neither binary -- so using any
of it meant cloning the repository and building in a container. This
release carries diluvium_host_linux_static_x86_64 and
diluvium_rest_plugin_linux_static_x86_64 as release artifacts,
checksummed alongside everything else.

That gap was not academic. It cost three separate round trips
downstream, and every one of them looked the same from the outside: a
host older than the configuration it was handed refuses a key it does
not know, correctly and by name, and the refusal reads like a bad
config rather than an old binary.

So the other half of this release is being able to tell those apart.
diluvium-host --version answers which build it is, and the startup
banner leads with it, so the line above any refusal already says which
binary is doing the refusing.

Nothing in the runtime changed. This is build 8's feature set, made
obtainable.

Added

• diluvium_host_linux_static_x86_64 -- the generic host, fully
  static musl, so it runs on an Alpine older than the builder with no
  libc to match and no shared SQLite. This is the binary the capability
  model lives in: connectors, the listener, the driven swarm. The
  installer still ships only the CLI, which is a separate gap
  (doc/BUILD7.md §5).
• diluvium_rest_plugin_linux_static_x86_64 -- outbound HTTP and
  HTTPS as a plugin, so build 8's plugin channel has something runnable
  to point at. It links OpenSSL and the host links none, which is the
  arrangement the channel exists to make possible.
• diluvium-host --version, and the build in the startup banner.
  The build number now reaches a compiled artifact for the first time:
  VERSION stays the single source of truth and the makefile passes it
  in, so there is no second copy to drift.

Fixed

• host/build-musl.sh and host/Dockerfile.musl build and export the rest plugin beside the host, rather than the host alone.

Upgrading

Snapshots taken by 5.5.1_build8 restore on this build, and so do
build7's: the permanents fingerprint has not moved since build 7, and
no guest-visible surface changed here at all.

The host and the rest plugin are x86_64 Linux only. The aarch64 and
armv7l CLI builds go through QEMU, and the host additionally needs
sqlite-static for those arches while the plugin needs
openssl-libs-static. Other platforms still build from source.

A consumer should pin a version and verify the checksum. Every
artifact is listed in the release's SHA256SUMS.txt. Following
latest means being unable to tell a Diluvium regression from your
own.

Built from commit 760783d23fd5.

Download guide

Platform	File	Notes
Linux (standard)	diluvium_linux_static_x86_64	Static; works on Ubuntu, Fedora, CentOS, Arch
Raspberry Pi 3/4/5	diluvium_linux_static_aarch64	64-bit OS only
Raspberry Pi Zero	diluvium_linux_static_armv7l	32-bit ARM
macOS (Apple silicon)	diluvium_darwin_arm64	M1/M2/M3/M4
macOS (Intel)	diluvium_darwin_x86_64
Windows	diluvium_windows_x86_64.exe	64-bit
WASI	diluvium_wasi.wasm	Needs a runtime with wasm exception-handling (wasmtime 28+ with -W exceptions=y)
Browser	libdiluvium_wasm_unknown.a	wasm32-unknown-unknown static library

Each platform also ships a diluvium_compiler_* binary (luac
with the -r analysis report flag) and a libdiluvium_*.a static
library for embedding.

Verifying a download

sha256sum -c SHA256SUMS.txt --ignore-missing

BUILDINFO.txt records the exact commit, build time and workflow run.

---