Motivation
CI currently follows a rolling Zig 0.17 development build. Upstream compiler and standard-library API changes can break the default branch without repository changes, as happened with recent Build, allocator, and type-reflection APIs.
Proposed work
- Decide whether the project targets a pinned development build, a tested range, or latest Zig master.
- If tracking latest master, add a scheduled compatibility job and a documented update process.
- Consider separating required pinned CI from an allowed-to-fail latest-master job.
- Record the supported Zig version in package metadata and documentation.
- Add a release checklist item for toolchain compatibility.
Acceptance criteria
- Contributors can determine the supported Zig version from one documented location.
- Required CI is reproducible.
- Latest-master breakage is detected without unexpectedly blocking unrelated changes, unless latest-master support is the explicit policy.
- Toolchain upgrades include compatibility notes.