You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Build: support current Zig 0.17.0-dev stdlib API changes #626
GitHub Actions now installs Zig 0.17.0-dev.1811. The current tree compiles locally with 0.17.0-dev.1441, but CI fails every build-based job with seven compile errors:
three std.ArrayListUnmanaged.getLast calls in FnScope after that convenience API was removed;
three cached Matcher.findFrom calls that exceed the newer one-level implicit pointer-dereference rule;
Dependency progress: zig-regex@87e9ca2 is now on its main, and zig-regex#21 is closed after its complete suite passed on both dev.1441 and the exact CI dev.1811 compiler.
Integrated validation so far: the full zig-js unit artifact compiles on 0.17.0-dev.1811+6716bf52e, and zig build test -Dtest-filter=compiler passes 71/71. This clears all seven compiler diagnostics observed in CI. RegExp-focused and full parallel unit validation remain before landing the zig-js commit.
changed the title [-]Build: support Zig 0.17.0-dev.1811 stdlib API changes[/-][+]Build: support current Zig 0.17.0-dev stdlib API changes[/+]on Aug 20, 2026
Reopened after the next CI run resolved zig@0.17.0-dev to 0.17.0-dev.1818+7051f8e73. The dev.1811 fixes removed the compiler stack errors, but dev.1818 tightened method-call adjustment again: the three cached matcher calls now need fully qualified invocation. CI also correctly revealed that all workflow jobs still pin zig-regex@2de4668, so the landed dependency fix was not consumed.
Follow-up scope is exact: use Regex.Matcher.findFrom(matcher, ...) to avoid implicit pointer adjustment on both dev.1441/dev.1811/dev.1818, and advance every audited CI zig-regex checkout to 87e9ca2. No JS semantics or job/queue surfaces are involved.
Final dev.1818 follow-up landed on main in 6cb02043.
This closes the gap exposed by CI run 32336603425:
all three cached matcher calls use fully qualified receiver invocation;
seven CI plus one performance workflow now consume zig-regex@87e9ca2;
dependency inventory pins match those eight checkout sites.
Final local evidence: dev.1818 compiler 71/71 and RegExp 21/21; dev.1441 RegExp 21/21; full parallel units 1,738 pass / 1 skip / 0 fail / 0 leak; dependency audit 15 edges / 0 migrations / 60 tools. A fresh main CI run is now queued.
Reopened for the Linux-specific dev.1818 link edge from fresh CI run 32337623853. Source compilation now succeeds; the remaining four diagnostics are duplicate linker references to __register_frame / __deregister_frame from jit.gdb_jit, which macOS does not exercise. I am tracing the owned unwind-provider link contract now. This is separate from the matcher/zig-regex fixes and will be validated on Linux before the next push.
Linux dev.1818 linker follow-up landed in 6557c9bd.
The x86_64-linux unit artifact now links without __register_frame, __deregister_frame, or _Unwind_Find_FDE references. The supported Mach-O path remains exact: publication-filter tests pass 31/31 on both dev.1818 and dev.1441, including dynamic FDE registration/retirement and concurrent descriptor publication. Full local units pass 1,738 / 1 skip / 0 fail / 0 leak; dependency audit remains clean.
A new main CI run will confirm Linux execution across the complete matrix.
Activity
chrisbbreuer commentedon Aug 20, 2026
Dependency progress:
zig-regex@87e9ca2is now on itsmain, and zig-regex#21 is closed after its complete suite passed on both dev.1441 and the exact CI dev.1811 compiler.Integrated validation so far: the full zig-js unit artifact compiles on
0.17.0-dev.1811+6716bf52e, andzig build test -Dtest-filter=compilerpasses 71/71. This clears all seven compiler diagnostics observed in CI. RegExp-focused and full parallel unit validation remain before landing the zig-js commit.chrisbbreuer commentedon Aug 20, 2026
Landed on
mainind46ed71e, paired withzig-regex@87e9ca2.Final validation:
0.17.0-dev.1811+6716bf52e: compiler filter 71/71; RegExp filter 21/21test-parallel1,738 passed, 1 skipped, 0 failed, 0 leakedThe push has triggered a new main CI run for repository-wide confirmation.
[-]Build: support Zig 0.17.0-dev.1811 stdlib API changes[/-][+]Build: support current Zig 0.17.0-dev stdlib API changes[/+]chrisbbreuer commentedon Aug 20, 2026
Reopened after the next CI run resolved
zig@0.17.0-devto0.17.0-dev.1818+7051f8e73. The dev.1811 fixes removed the compiler stack errors, but dev.1818 tightened method-call adjustment again: the three cached matcher calls now need fully qualified invocation. CI also correctly revealed that all workflow jobs still pinzig-regex@2de4668, so the landed dependency fix was not consumed.Follow-up scope is exact: use
Regex.Matcher.findFrom(matcher, ...)to avoid implicit pointer adjustment on both dev.1441/dev.1811/dev.1818, and advance every audited CI zig-regex checkout to87e9ca2. No JS semantics or job/queue surfaces are involved.chrisbbreuer commentedon Aug 20, 2026
Final dev.1818 follow-up landed on
mainin6cb02043.This closes the gap exposed by CI run 32336603425:
zig-regex@87e9ca2;Final local evidence: dev.1818 compiler 71/71 and RegExp 21/21; dev.1441 RegExp 21/21; full parallel units 1,738 pass / 1 skip / 0 fail / 0 leak; dependency audit 15 edges / 0 migrations / 60 tools. A fresh main CI run is now queued.
chrisbbreuer commentedon Aug 20, 2026
Reopened for the Linux-specific dev.1818 link edge from fresh CI run 32337623853. Source compilation now succeeds; the remaining four diagnostics are duplicate linker references to
__register_frame/__deregister_framefromjit.gdb_jit, which macOS does not exercise. I am tracing the owned unwind-provider link contract now. This is separate from the matcher/zig-regex fixes and will be validated on Linux before the next push.chrisbbreuer commentedon Aug 20, 2026
Linux dev.1818 linker follow-up landed in
6557c9bd.The x86_64-linux unit artifact now links without
__register_frame,__deregister_frame, or_Unwind_Find_FDEreferences. The supported Mach-O path remains exact: publication-filter tests pass 31/31 on both dev.1818 and dev.1441, including dynamic FDE registration/retirement and concurrent descriptor publication. Full local units pass 1,738 / 1 skip / 0 fail / 0 leak; dependency audit remains clean.A new main CI run will confirm Linux execution across the complete matrix.