the download page links and index.json are out of sync for the latest nightly/master version

[Techatrix]

At the time of publishing this issue, the https://ziglang.org/download/index.json currently has 0.15.0-dev.636+35ba8d95a as the latest nightly version. The download page however points to 0.15.0-dev.631+9a3540d61. And the index.json that is committed to source control in this repository is still stuck at 0.15.0-dev.621+a63f7875f.

[nektro]

timestamp of recent publishes

0.15.0-dev.589+23c817548/                          20-May-2025 20:03       -
0.15.0-dev.621+a63f7875f/                          21-May-2025 06:03       -
0.15.0-dev.631+9a3540d61/                          24-May-2025 18:17       -
0.15.0-dev.635+7dbd21bd5/                          25-May-2025 07:03       -
0.15.0-dev.636+35ba8d95a/                          25-May-2025 18:03       -

[nektro]

build tarballs action, which would usually re-sync them all, is failing

2025-05-25T17:21:34.0719986Z info: running /home/ci/actions-runner/_work/zig-bootstrap/out/host/bin/zig...
2025-05-25T17:21:38.6389152Z thread 3723441 panic: failed to write documentation/master/std/index.html.gz: FileNotFound
2025-05-25T17:21:38.8131896Z /home/ci/deps/zig-linux-x86_64-0.14.0/lib/std/posix.zig:1825:23: 0x116d6dd in openatZ (build-commit)
2025-05-25T17:21:38.8132806Z             .NOENT => return error.FileNotFound,
2025-05-25T17:21:38.8133306Z                       ^
2025-05-25T17:21:38.8134430Z /home/ci/deps/zig-linux-x86_64-0.14.0/lib/std/fs/Dir.zig:1037:16: 0x11e37aa in createFileZ (build-commit)
2025-05-25T17:21:38.8135379Z     const fd = try posix.openatZ(self.fd, sub_path_c, os_flags, flags.mode);
2025-05-25T17:21:38.8135961Z                ^
2025-05-25T17:21:38.8136592Z /home/ci/deps/zig-linux-x86_64-0.14.0/lib/std/fs/Dir.zig:996:5: 0x11dfc17 in createFile (build-commit)
2025-05-25T17:21:38.8137380Z     return self.createFileZ(&path_c, flags);
2025-05-25T17:21:38.8137794Z     ^
2025-05-25T17:21:38.8138408Z /home/ci/deps/zig-linux-x86_64-0.14.0/lib/std/fs/Dir.zig:2432:16: 0x11d90bd in writeFile (build-commit)
2025-05-25T17:21:38.8139303Z     var file = try self.createFile(options.sub_path, options.flags);
2025-05-25T17:21:38.8139832Z                ^
2025-05-25T17:21:38.8140813Z /home/ci/actions-runner/_work/www.ziglang.org/www.ziglang.org/.github/workflows/build-commit.zig:772:14: 0x11e1ebe in gzipCopy (build-commit)
2025-05-25T17:21:38.8141952Z         fatal("failed to write {s}: {s}", .{ new_name, @errorName(err) });
2025-05-25T17:21:38.8142495Z              ^
2025-05-25T17:21:38.8143361Z /home/ci/actions-runner/_work/www.ziglang.org/www.ziglang.org/.github/workflows/build-commit.zig:325:13: 0x11df2fa in main (build-commit)
2025-05-25T17:21:38.8144468Z     gzipCopy(&env_map, bootstrap_dir, "std/index.html", std_docs_dir);
2025-05-25T17:21:38.8145004Z             ^
2025-05-25T17:21:38.8145688Z /home/ci/deps/zig-linux-x86_64-0.14.0/lib/std/start.zig:656:37: 0x11c9e5a in posixCallMainAndExit (build-commit)
2025-05-25T17:21:38.8146683Z             const result = root.main() catch |err| {
2025-05-25T17:21:38.8147135Z                                     ^
2025-05-25T17:21:38.8147816Z /home/ci/deps/zig-linux-x86_64-0.14.0/lib/std/start.zig:271:5: 0x11c9a0d in _start (build-commit)
2025-05-25T17:21:38.8148554Z     asm volatile (switch (native_arch) {
2025-05-25T17:21:38.8148944Z     ^
2025-05-25T17:21:38.8149217Z ???:?:?: 0x0 in ??? (???)
2025-05-25T17:21:38.8191615Z /home/ci/actions-runner/_work/_temp/ace4aa65-0f34-423e-a590-7e57181fb172.sh: line 1: 3723441 Aborted                 nice -10 /home/ci/deps/zig-linux-x86_64-0.14.0/zig run ./.github/workflows/build-commit.zig -- /var/www/html ./.github/workflows/index.json
2025-05-25T17:21:38.8345724Z ##[error]Process completed with exit code 134.

[leecannon]

Giving this a bump as multiple people on zigcord have been tripped up with the impression that (at the time of writing) zig-0.15.0-dev.1092+d772c0627 on the download page is the latest even though the index.json already has 0.15.0-dev.1177+9abc3232a.