From 73f965471fd9536ce671f6733c2551e6ed8aa70f Mon Sep 17 00:00:00 2001 From: Stephen Gutekanst Date: Mon, 30 Dec 2024 20:22:07 -0700 Subject: [PATCH] nominate Zig 2024.11.0-mach Signed-off-by: Stephen Gutekanst --- content/docs/nominated-zig.md | 2 -- content/docs/zig-version.md | 2 +- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/content/docs/nominated-zig.md b/content/docs/nominated-zig.md index a50ccc5..7bc060b 100644 --- a/content/docs/nominated-zig.md +++ b/content/docs/nominated-zig.md @@ -89,8 +89,6 @@ Periodically, the question comes up: why *not* just use stable Zig versions? The ### 2024.11.0-mach -**IN-PROGRESS:** This version is currently being nominated, see [the tracking issue](https://github.com/hexops/mach/issues/1287) for details. Once everything looks good, the new Zig version is confirmed to be working with Mach, we will declare success, close the issue, and remove this in-progress warning. - Zig `2024.11.0-mach` and `0.14.0-dev.2577+271452d22` are identical. Install it using [zigup](https://github.com/marler8997/zigup): diff --git a/content/docs/zig-version.md b/content/docs/zig-version.md index efb1d89..0c6b873 100644 --- a/content/docs/zig-version.md +++ b/content/docs/zig-version.md @@ -17,7 +17,7 @@ _We encourage using Mach nightly (`main`, rather than a tagged release) for now. | Mach version | Zig version | |--------------|---------------------------------------------------------| -| latest main | [Zig 2024.10.0-mach](/docs/nominated-zig/#2024100-mach) | +| latest main | [Zig 2024.11.0-mach](/docs/nominated-zig/#2024110-mach) | | v0.4 | [Zig 2024.5.0-mach](/docs/nominated-zig/#202450-mach) | | v0.3 | [Zig 2024.1.0-mach](/docs/nominated-zig/#202410-mach) | | v0.2 | v0.11.0 |