Why
zig-js moved to 0.17.0-dev.1441+d5181a9c9, and Home will eventually consume zig-js — so align Home's toolchain pin to match, keeping the two in sync.
Verified locally (macos-arm64)
The 166-commit jump 1275→1441 has no breaking changes for Home:
zig build debugcompiles with zero errors- resulting binary runs clean across every path:
- Home-language:
home run examples/hello.home→Hello, Home! - JSC runtime:
home test test/js/node/path/basename.test.js→ 4/0 - CLI run-flag path:
parse_args/default-args.test.mjs→ 8/0
- Home-language:
What changed (exact version-string swap, 19 refs / 13 files)
pantry.json/pantry.lock(pkgx-style lock — no embedded hashes to regen)package.json,packages/comptime/home.toml- 5 CI workflows (
mlugg/setup-zigversion): release, conformance-gate, fuzz-nightly, ci, dataplane-bench - version-guard scripts:
run_tests.sh,check-test-count.sh,tools/ts_parity_snapshot.py - doctor/help text in
src/main.zig
What this PR's CI adds
Local proof was macos-arm64 only — CI here validates the full platform matrix under 1441. Safe to merge once green.