Skip to content

fix(ci): pin Zig version to 0.15.2 instead of nightly master#241

Closed
gumruyanzh wants to merge 1 commit intojetzig-framework:mainfrom
gumruyanzh:fix-ci-zig-version
Closed

fix(ci): pin Zig version to 0.15.2 instead of nightly master#241
gumruyanzh wants to merge 1 commit intojetzig-framework:mainfrom
gumruyanzh:fix-ci-zig-version

Conversation

@gumruyanzh
Copy link

Summary

  • Pin CI Zig version from master (nightly) to 0.15.2 (latest stable)
  • Fixes CI failures that have been occurring daily since Zig 0.16-dev introduced breaking changes

Problem

CI has been failing on every run since mid-February. The workflow uses version: master which resolves to Zig 0.16.0-dev, but the project and its dependencies (zmpl, etc.) target Zig 0.15.x. Breaking changes in 0.16-dev include:

  • discard of capture; omit it instead (language change in zmpl/Data.zig)
  • struct 'fs' has no member named 'cwd' (std lib API change in zmpl/build.zig)
  • Package hash format changes causing hash mismatch errors

Approach

Pin to 0.15.2 which is the latest stable Zig release compatible with the project. The existing zig-0.16 tracking branch (issue #231) handles the nightly migration separately.

Test plan

  • Local build and tests pass with Zig 0.15.2
  • CI should pass on all three platforms (ubuntu, macos, windows)

🤖 Generated with Claude Code

CI has been failing daily since the project targets Zig 0.15.x but the
workflow was using `version: master` which now resolves to 0.16.0-dev.
Zig 0.16 nightly has breaking changes that affect dependencies (zmpl):

  - `discard of capture; omit it instead` (language change)
  - `struct 'fs' has no member named 'cwd'` (std lib API change)
  - Package hash format changes causing hash mismatches

Pin to 0.15.2 (latest stable release compatible with the project) to
restore CI. A separate zig-0.16 tracking branch already exists for the
nightly migration effort (see issue #231).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@gumruyanzh gumruyanzh closed this by deleting the head repository Feb 27, 2026
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