Support the Zig 0.17 lane - #39
Merged
Merged
Conversation
Adds "0.17" to #ZigLane and a matching case in build.zig laneMatchesCurrent, so a project can declare toolchain.zig.lanes: ["0.17"]. Also fixes a real 0.17 break: std.ArrayList became fully unmanaged, so `step.dependencies.append(x)` now needs an allocator. Switch to `step.dependOn(x)`, the stable API across 0.14 through 0.17, which is what the code meant anyway. Validated by building a corpus repo that requires 0.17 (ZigEmbeddedGroup/microzig tools/flags) through the full Azazel flow on 0.17.0-dev: gen_build_spec then `zig build` produces the static library. The dependOn change is verified on 0.16 locally (build plus the 35-test suite pass); CI covers 0.14.1 / 0.15.2 / 0.16.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
"0.17"to#ZigLane(schema.cue) and a matching case inbuild.zig'slaneMatchesCurrent, so a project can declaretoolchain.zig.lanes: ["0.17"].It also fixes a genuine 0.17 break:
std.ArrayListbecame fully unmanaged, sostep.dependencies.append(x)now requires an allocator. Switched tostep.dependOn(x), the stable API across 0.14 through 0.17 and what the code meant anyway.Why
Unblocks corpus repos that require Zig 0.17-dev.
ZigEmbeddedGroup/microzigis the first: itsminimum_zig_versionis 0.17.0-dev and its sources use 0.17-only std APIs, so it could not be modeled until Azazel recognized the lane.Validation
microzig'stools/flagsslice through the full Azazel flow on 0.17.0-dev (gen_build_spec.shthenzig buildproduceszig-out/lib/libflags.a).dependOnchange is verified locally on 0.16 (build plus the 35-test suite pass). CI covers 0.14.1 / 0.15.2 / 0.16.0; those released lanes stay the CI matrix (0.17 is a dev build and a moving target).🤖 Generated with Claude Code