Zig moves all package management out of the compiler into the build system

In its June 30, 2026 devlog, the Zig project announced it has moved all package-management functionality out of the compiler executable. The zig build, zig fetch, zig init and zig libc subcommands now run inside the build system's "maker" process — which already exists as a separate process for running users' build.zig scripts, making it the natural home for package-management logic.

Key points

• Large components now ship as source in the maker: package fetching, the HTTP client, TLS/crypto, git protocol support, compression libraries (xz, gzip, zstd, flate, zip) and build-config parsing/validation.
• Patchable without rebuilding the compiler: because this code is now source-based, users and contributors can modify and tinker with it far more easily.
• Safer networking: the maker compiles in ReleaseSafe mode, enabling safety checks during network operations.
• CPU optimizations: the crypto used for networking and file hashing can now take advantage of host-specific CPU instructions — even rare ones that software normally can't depend on when distributed.
• The Zig executable shrinks ~4% (14.1 → 13.5 MiB in ReleaseSmall). The --maker-opt flag becomes the ZIG_DEBUG_MAKER env var, and --zig-lib-dir becomes ZIG_LIB_DIR.