Repository navigation
Celtium 0.2.3 — Multi-OS verified release
Released 2026-11-16 · tag v0.2.3 · previous v0.2.2
0.2.2-rc1 fixed a Windows-only failure whose root cause was a Linux-only assumption in the readable-range
guard. This release finishes that job: the whole repository was audited for OS-specific assumptions, the
defects found were fixed, and CI now runs the test suite on Windows and macOS as well as Linux, so the next
assumption of that kind fails a build instead of shipping.
What "multi-OS verified" means here
Exactly this, and no more: the complete celtium-vulkan test suite (94 suites / 462 tests) and the
repository's OS-portable checks (check_agent_docs.py, instrument-index.py --check) pass with identical
results on CI runners for all three operating systems — Ubuntu, Windows (windows-latest) and macOS
(macos-latest) — in the same workflow run
(run 43877915571). It does not mean the
game itself was run on real hardware on those systems; see Known limits.
Fixed
- The test build no longer assumes a Linux host. The
celtium-vulkantest runtime pinned the LWJGL
natives classifier tonatives-linux, so on a Windows or macOS host the test JVM extracted a Linux.so
and the shaderc binding failed its initialiser — the suite could not run off Linux at all. The classifier
now follows the host OS and architecture. - The shader compiler is findable on Windows and current installs. The PATH lookup probed only the bare
program name, which never matches a Windows.exe, and the candidate list knew only the pre-rename name
glslangValidator— the current Khronos Windows release ships onlyglslang.exe. The probe now tries the
.exeform on Windows,glslangis a candidate on every OS, and the not-found message names the macOS
and Windows install routes alongside Debian/Ubuntu. - The readable-range guard now covers macOS. The guard behind the 0.2.2-rc1 fix had providers for Linux
(/proc/self/maps) and Windows (VirtualQuery) only; on macOS every client-memory draw not covered by an
owned-buffer publication was refused — the same failure class as the Windows bug, one OS over. A macOS
provider now walks VM regions withmach_vm_region(FFM), behind the same testable seam as the other
providers. The new CI leg caught this before it shipped: its first run was green on Windows and red on
exactly the three client-array tests on macOS. - The audit's remaining findings were classified as by-design with safe degradation (for example, the guard
still refuses by default on any OS beyond the three above) or checked and clear; the full classification
is recorded with the change history.
CI
- New
vulkan-multi-osmatrix job (Windows, macOS) running:celtium-vulkan:testplus the OS-portable
check scripts, with glslang 16.6.0 pinned from the official Khronos release archives. The legs
deliberately rely on the build's own PATH resolution for the shader compiler, so the Windows.exe
lookup is itself under test. The existing Ubuntu jobs are unchanged, and the Forge packaging build
(:forge122:packageJar) stays on the Ubuntu legs — the shipped jar is platform-independent.
Known limits
- No real-machine in-game verification on Windows or macOS: actual rendering under a real install (for
example EfficientEntities on Windows, or MoltenVK on macOS), frame-time impact, and the FFM bindings
under the game's own JVM remain unverified on hardware. The CI legs exercise the bindings in a test JVM
on hosted runners; they narrow the class of bug that can ship, they do not close it.