You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
at the time of writing, Zig 0.12.0 is the latest release and latest nightly build.
When setup-zig is trying to install the latest nightly build (which should be 0.12.0) it instead installs an older development build.
Run goto-bus-stop/setup-zig@v2
with:
version: master
cache: true
attempting restore of zig-zig-linux-x86_64-0.12.0 to /opt/hostedtoolcache/zig/master/x64
Cache Size: ~66 MB (69169481 B)
/usr/bin/tar -xf /home/runner/work/_temp/c42ccf7a-c4ea-4409-b850-bf52274b7af4/cache.tzst -P -C /home/runner/work/zls/zls --use-compress-program unzstd
Received 69169481 of 69169481 (100.0%), 66.0 MBs/sec
Cache restored successfully
using cached zig install: /opt/hostedtoolcache/zig/master/x64
zig installed at /opt/hostedtoolcache/zig/master/x64
Why does it successfully restore the cache when installing 0.12.0 and choose a development build instead of 0.12.0? And why does a newer run install an older Zig version?
I tried deleting any recent Github action caches but that didn't help. Adding cache: false did fix the issue.
The text was updated successfully, but these errors were encountered:
at the time of writing, Zig 0.12.0 is the latest release and latest nightly build.
When setup-zig is trying to install the latest nightly build (which should be 0.12.0) it instead installs an older development build.
https://ziglang.org/download/index.json
Run that installed
0.12.0-dev.3686+3adfaf91f
on Apr 20, 2024, 12:51 PM GMT+2:Run that installed
0.12.0-dev.3676+21a6a1b0
on Apr 20, 2024, 5:43 PM GMT+2Why does it successfully restore the cache when installing 0.12.0 and choose a development build instead of 0.12.0? And why does a newer run install an older Zig version?
I tried deleting any recent Github action caches but that didn't help. Adding
cache: false
did fix the issue.The text was updated successfully, but these errors were encountered: