# Zig master version out of date on official download page

**URL:** <https://ziggit.dev/t/zig-master-version-out-of-date-on-official-download-page/13905>\
**Category:** Help\
**Tags:** zig-master\
**Created:** [January 11, 2026, 9:15pm UTC](https://ziggit.dev/t/zig-master-version-out-of-date-on-official-download-page/13905 "2026-01-11T21:15:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![paralogismos](https://ziggit.dev/letter_avatar_proxy/v4/letter/p/a3d4f5/32.png) [@paralogismos](https://ziggit.dev/u/paralogismos)\
**Post date:** [January 11, 2026, 9:15pm UTC](https://ziggit.dev/t/zig-master-version-out-of-date-on-official-download-page/13905/1 "2026-01-11T21:15:37Z")

</div>

I updated to what I thought was the latest Zig master today, then cloned a fresh version of Ziglings and ran `zig build`. Ziglings responded with: “Ziglings requires development build `0.16.0-dev.2075` or higher.” This seemed strange to me because the latest development build shown on the [official download page](https://ziglang.org/download/), and the one which I had just installed, was `0.16.0-dev.2040+c475f1fcd`. I cleared my browser cache to see if something was preventing an update, but no luck. After scratching my head for a minute, I looked at the [JSON version of the page](https://ziglang.org/download/index.json) and found that the most recent development build was `0.16.0-dev.2145+ec25b1384`, so I grabbed that and Bob’s your uncle. There was no .minisig file on the JSON page so I had to content myself with a sha256 checksum, but at least Ziglings builds now.

I’ve downloaded the master version many, many times like this and never had a problem before. Is there some kind of bug on the official download page, or am I missing something?

---

<div class="post-metadata">

**Author:** ![rpkak](https://ziggit.dev/letter_avatar_proxy/v4/letter/r/a4c791/32.png) [@rpkak](https://ziggit.dev/u/rpkak)\
**Post date:** [January 11, 2026, 9:19pm UTC](https://ziggit.dev/t/zig-master-version-out-of-date-on-official-download-page/13905/2 "2026-01-11T21:19:40Z")

</div>

> [@Zig versions](https://ziggit.dev/t/zig-versions/13844/4):
>
> Two Zulip conversations: The first contains an explanation, why this changed with codeberg: [#ecosystem \> ziglang.org/download is out of date](https://zsf.zulipchat.com/#narrow/channel/454446-ecosystem/topic/ziglang.2Eorg.2Fdownload.20is.20out.20of.20date/with/565593639)[#ecosystem \> prebuilt binary links have gone out of date](https://zsf.zulipchat.com/#narrow/channel/454446-ecosystem/topic/prebuilt.20binary.20links.20have.20gone.20out.20of.20date/with/566267513)

Also: You can add `.minisig` to the end of the urls to download the signature.

---

<div class="post-metadata">

**Author:** ![paralogismos](https://ziggit.dev/letter_avatar_proxy/v4/letter/p/a3d4f5/32.png) [@paralogismos](https://ziggit.dev/u/paralogismos)\
**Post date:** [January 11, 2026, 9:25pm UTC](https://ziggit.dev/t/zig-master-version-out-of-date-on-official-download-page/13905/3 "2026-01-11T21:25:28Z")

</div>

Thanks for the link; that explains it. Also, thanks for the `.minisig` tip: I should have thought of that!