Auto-install pinned Zig toolchain in setup + devcontainer#38
Merged
Conversation
The Zig FFI bridge is half of the ABI-FFI standard, but nothing installed Zig: .tool-versions only lists it (commented), setup.sh stops at `just`, and the devcontainer's `postCreateCommand: just deps` referenced a `deps` recipe that did not exist. Unlike the other toolchain pieces, Zig is not distributed via GitHub releases, so it must come from ziglang.org. Add scripts/install-zig.sh: an idempotent, fail-soft installer for the pinned Zig 0.14.0 (arch/OS-aware, uses the system CA store the agent proxy populates, never --insecure). If ziglang.org is not on the session's egress allowlist the download 403s and the script exits 0 with an actionable message, so it never blocks setup or a session. Wire it in via the two paths the project already uses: a "Step 1b" in setup.sh (where the template exposes that step), and a new `deps` Justfile recipe backing the devcontainer postCreateCommand. Once ziglang.org is allowlisted, future setups and dev containers install Zig automatically. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019xMKB3T4Vo5FYC7Czx3JSH
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
2 participants
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.
What & why
The Zig FFI bridge is half of the ABI-FFI standard, but nothing installed Zig —
.tool-versionsonly lists it (commented),setup.shstopped atjust, and the devcontainer'spostCreateCommand: just depsreferenced adepsrecipe that didn't exist. And Zig is not distributed via GitHub releases, so it must come fromziglang.org, which isn't on the agent egress allowlist by default.Change
scripts/install-zig.sh— idempotent, fail-soft installer for the pinned Zig 0.14.0 (arch/OS-aware, uses the proxy-populated system CA store, never--insecure). Ifziglang.orgis blocked it 403s and exits 0 with an actionable message, so it never blocks setup.setup.sh— adds a Zig install step (where the template exposes one).Justfile— newdepsrecipe (install Zig +cargo fetch) backing the devcontainerpostCreateCommand: just deps.Once
ziglang.orgis allowlisted, future setups/dev-containers install Zig automatically. Part of a family-wide sweep; mirrors the merged iseriser reference (#70).CI note
The
rust-ciandHypatiachecks are pre-existing estate-infra reds (the reusable rust-ci workflow's emptytoolchaininput, and the Hypatia analyzer failing to compile its own Elixir source) — neither is caused by this shell/Justfile change.🤖 Generated with Claude Code
https://claude.ai/code/session_019xMKB3T4Vo5FYC7Czx3JSH
Generated by Claude Code