From a47044f33ae5c794ddc917415d06169f26279cb4 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 27 Jun 2026 22:18:45 +0000 Subject: [PATCH] fix(ci): use the pinned Julia 1.11.5 in the ABI-FFI gate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #174's Julia install pointed $GITHUB_PATH at /tmp/julia-1.11.5-linux-x86_64/bin, but the official tarball extracts to julia-1.11.5/. That path never existed, so the gate silently ran on the runner's pre-installed Julia and the version pin was a no-op — harmless today, but wasteful and not reproducible (it would break if the runner image ever drops Julia). Point $GITHUB_PATH at /tmp/julia-1.11.5/bin, and echo `julia --version` in the gate step so the CI log shows the pinned 1.11.5 is actually on PATH. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01JdqVWGSSv36Ph8ZWvizGMp --- .github/workflows/abi-ffi-gate.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/abi-ffi-gate.yml b/.github/workflows/abi-ffi-gate.yml index 730a8d5..f647ba6 100644 --- a/.github/workflows/abi-ffi-gate.yml +++ b/.github/workflows/abi-ffi-gate.yml @@ -25,9 +25,11 @@ jobs: run: | curl -fsSL https://julialang-s3.julialang.org/bin/linux/x64/1.11/julia-1.11.5-linux-x86_64.tar.gz -o /tmp/julia.tar.gz tar -xf /tmp/julia.tar.gz -C /tmp - echo "/tmp/julia-1.11.5-linux-x86_64/bin" >> "$GITHUB_PATH" + echo "/tmp/julia-1.11.5/bin" >> "$GITHUB_PATH" - name: Run ABI-FFI gate - run: julia scripts/abi-ffi-gate.jl + run: | + julia --version # confirms the pinned 1.11.5 is on PATH, not the runner default + julia scripts/abi-ffi-gate.jl zig-build: name: Zig FFI builds + tests (Zig 0.14.0)