Both version constants are hardcoded and were last bumped for the v2026.3.2 release, while the latest release is v2026.5.29:
src/main.zig:7 — const version = "2026.3.2"; (reported by --version)src/api.zig:8 — const version = "2026.3.2"; (reported by GET /health)
So a v2026.5.29 binary identifies itself as 2026.3.2 in both the CLI and the health endpoint.
Suggested fix: inject the version at build time via a build.zig option (b.option([]const u8, "version", ...)) exposed through a module/@import("build_options"), so there is a single source of truth wired into the release workflow, instead of two constants that must be bumped by hand.
Both version constants are hardcoded and were last bumped for the v2026.3.2 release, while the latest release is v2026.5.29:
src/main.zig:7—const version = "2026.3.2";(reported by--version)src/api.zig:8—const version = "2026.3.2";(reported byGET /health)So a v2026.5.29 binary identifies itself as 2026.3.2 in both the CLI and the health endpoint.
Suggested fix: inject the version at build time via a
build.zigoption (b.option([]const u8, "version", ...)) exposed through a module/@import("build_options"), so there is a single source of truth wired into the release workflow, instead of two constants that must be bumped by hand.