Skip to content

fix(ci): resolve zig via PATH when mise is unavailable - #48

Merged
pythoninthegrass merged 1 commit into
mainfrom
fix-355.1-zig-ci
Sep 11, 2026
Merged

pythoninthegrass merged 1 commit into
mainfrom
fix-355.1-zig-ci

Conversation

@pythoninthegrass

Copy link
Copy Markdown
Collaborator

Summary

  • The new zig CI job (from feat(zig): pin zig 0.15.2 via mise and wire taskfile + CI job #47 / TASK-355.1) failed on its first real run: _check-zig-version only resolves zig through mise which zig, but CI installs Zig directly via mlugg/setup-zig@v2 onto PATH — there is no mise on the Blacksmith runner at all.
  • taskfiles/zig.yml's ZIG var now falls back to command -v zig when mise can't resolve it, and _check-zig-version verifies whichever binary was found (mise-managed or PATH) against the pinned version in .tool-versions.

Verification

  • Ran task zig:lint, task zig:test, task zig:build locally with mise present (unchanged behavior).
  • Simulated the CI condition by stripping mise off PATH while leaving zig/task binaries reachable directly — confirmed the fallback resolves zig via PATH and all three tasks pass.

Test plan

  • task zig:lint / task zig:test / task zig:build pass locally (mise-resolved)
  • Same commands pass with mise removed from PATH (PATH-resolved, simulating CI)
  • CI zig job goes green on this PR

CI installs Zig directly via mlugg/setup-zig onto PATH (no mise on the
Blacksmith runner), but _check-zig-version only ever tried mise which,
so the zig job failed immediately with "mise is not on PATH" in its
first real CI run.
@pythoninthegrass
pythoninthegrass merged commit 219c8ef into main Sep 11, 2026
6 of 8 checks passed
@pythoninthegrass
pythoninthegrass deleted the fix-355.1-zig-ci branch September 11, 2026 20:52
pythoninthegrass added a commit that referenced this pull request Sep 11, 2026
Records the zig CI job failure found and fixed in PR #48 (mise
unavailable on the Blacksmith runner) and the cold/warm cache
timings gathered via manual workflow_dispatch runs (44s cold, 23s
warm), completing the last open acceptance criterion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant