summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Boesch <chrboesch@noreply.codeberg.org>2026-04-15 14:33:47 +0200
committerChris Boesch <chrboesch@noreply.codeberg.org>2026-04-15 14:33:47 +0200
commit4746ccc1c89a03fff7c4b35d78dcb57b125c444a (patch)
treeb545cb66b0ac80c911e84a1aece251e7a4a61415
parentc6f18ba448089534763055189ed05f019bd4b7b8 (diff)
v0.16
-rw-r--r--README.md4
-rw-r--r--build.zig2
2 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index 35eadd4..4171284 100644
--- a/README.md
+++ b/README.md
@@ -45,7 +45,7 @@ Verify the installation and build number of `zig` like so:
```
$ zig version
-0.16.0-dev.xxxx+xxxxxxxxx
+0.17.0-dev.xxxx+xxxxxxxxx
```
Clone this repository with Git:
@@ -73,7 +73,7 @@ the appropriate tag.
The Zig language is under very active development. In order to be
current, Ziglings tracks **development** builds of the Zig
compiler rather than versioned **release** builds. The last
-stable release was `0.15.2`, but Ziglings needs a dev build with
+stable release was `0.16`, but Ziglings needs a dev build with
pre-release version "0.16.0" and a build number at least as high
as that shown in the example version check above.
diff --git a/build.zig b/build.zig
index 303b76b..0db108d 100644
--- a/build.zig
+++ b/build.zig
@@ -15,7 +15,7 @@ const print = std.debug.print;
// 1) Getting Started
// 2) Version Changes
comptime {
- const required_zig = "0.16.0-dev.2915";
+ const required_zig = "0.16.0";
const current_zig = builtin.zig_version;
const min_zig = std.SemanticVersion.parse(required_zig) catch unreachable;
if (current_zig.order(min_zig) == .lt) {