diff options
| author | Chris Boesch <[email protected]> | 2024-04-20 20:37:30 +0000 |
|---|---|---|
| committer | Chris Boesch <[email protected]> | 2024-04-20 20:37:30 +0000 |
| commit | ce0a6cc91c4bd883367e8b5990a48efb5bfd76c3 (patch) | |
| tree | 558455dd567c7800c60f5fa900fa5cd60a39adac | |
| parent | 8f36619bd7c2b8b0e6f653f575dd2ae9510c98f9 (diff) | |
| parent | c94eb33e4417aa1281d8f3c644ea7981112824d6 (diff) | |
| download | ziglings-ce0a6cc91c4bd883367e8b5990a48efb5bfd76c3.tar.xz ziglings-ce0a6cc91c4bd883367e8b5990a48efb5bfd76c3.zip | |
Merge pull request 'Switch to new zig dev release 0.13' (#81) from r013 into main
Reviewed-on: https://codeberg.org/ziglings/exercises/pulls/81
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -46,7 +46,7 @@ Verify the installation and build number of `zig` like so: ``` $ zig version -0.12.0-dev.xxxx+xxxxxxxxx +0.13.0-dev.xxxx+xxxxxxxxx ``` Clone this repository with Git: @@ -74,8 +74,8 @@ 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.11.0`, but Ziglings needs a dev build with -pre-release version "0.12.0" and a build number at least as high +stable release was `0.12.0`, but Ziglings needs a dev build with +pre-release version "0.13.0" and a build number at least as high as that shown in the example version check above. It is likely that you'll download a build which is _greater_ than |