From e76cfec5ea3e068c17ae6c0f868f5366c84e0157 Mon Sep 17 00:00:00 2001 From: Abhishek Krishna Date: Thu, 23 Apr 2026 15:50:53 +0530 Subject: [PATCH] ci: bump Zig to 0.14.1 so CI can build (`.root_module` is a 0.14 API) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Every CI run has failed since 2026-04-07 with the same error on all six matrix cells: build.zig:9:10: error: no field named 'root_module' in struct 'Build.ExecutableOptions' `build.zig` uses the 0.14 build-system API throughout — `b.addExecutable(.{ .root_module = b.createModule(...) })`, `b.addLibrary`, `b.addTest(.{ .root_module = ... })` — but `.github/workflows/ci.yml` pins the toolchain to 0.13.0, which doesn't know about the `root_module` field. Bumping `ZIG_VERSION` from "0.13.0" to "0.14.1" (latest 0.14 patch) lets the existing build.zig compile without touching any source. No other edits required. — [kcolbchain](https://kcolbchain.com) / [Abhishek Krishna](https://abhishekkrishna.com) --- .github/workflows/ci.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index d2f6cee..c237500 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -7,7 +7,11 @@ on: branches: [main] env: - ZIG_VERSION: "0.13.0" + # Pinned to 0.14.1: build.zig uses the 0.14 build-system API + # (`b.addExecutable(.{ .root_module = b.createModule(...) })`, `b.addLibrary`, + # `b.addTest(.{ .root_module = ... })`). On 0.13.0 every job fails with + # build.zig:9:10: error: no field named 'root_module' in struct 'Build.ExecutableOptions' + ZIG_VERSION: "0.14.1" jobs: test: