# 0.17.0 tagged :O

**URL:** <https://ziggit.dev/t/0-17-0-tagged-o/17790>\
**Category:** News\
**Created:** [October 2, 2026, 10:36am UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790 "2026-10-02T10:36:57Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![ultiman3rd](https://ziggit.dev/user_avatar/ziggit.dev/ultiman3rd/32/8222_2.png) [@ultiman3rd](https://ziggit.dev/u/ultiman3rd)\
**Post date:** [October 2, 2026, 10:36am UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/1 "2026-10-02T10:36:57Z")

</div>

[https://codeberg.org/ziglang/zig/src/tag/0.17.0](https://codeberg.org/ziglang/zig/src/tag/0.17.0)

[https://codeberg.org/ziglang/zig/tags](https://codeberg.org/ziglang/zig/tags)

---

<div class="post-metadata">

**Author:** ![vulpesx](https://ziggit.dev/user_avatar/ziggit.dev/vulpesx/32/3989_2.png) [@vulpesx](https://ziggit.dev/u/vulpesx)\
**Post date:** [October 2, 2026, 10:44am UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/2 "2026-10-02T10:44:13Z")

</div>

The builds and change notes are not yet up, so still fingers crossed that there aren’t any issues that delay it (or requires an immediate patch release _cough 0.15 cough_)

---

<div class="post-metadata">

**Author:** ![kracked](https://ziggit.dev/letter_avatar_proxy/v4/letter/k/e8c25b/32.png) [@kracked](https://ziggit.dev/u/kracked)\
**Post date:** [October 2, 2026, 2:53pm UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/3 "2026-10-02T14:53:05Z")

</div>

Shipping to production on a friday. Yikes.

---

<div class="post-metadata">

**Author:** ![yinameah](https://ziggit.dev/user_avatar/ziggit.dev/yinameah/32/8453_2.png) [@yinameah](https://ziggit.dev/u/yinameah)\
**Post date:** [October 2, 2026, 5:10pm UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/4 "2026-10-02T17:10:09Z")

</div>

I’ve read in another thread it will take around 22 hours for the binaries to be in the website.

So, while I wait patiently, I’ve been wondering : why does it takes such a lengthy-ish time?

Somehow I never wondered before, but I know it’s the same for the master builds.  
Anybody familiar with the release process internal that would want to enlighten me?

---

<div class="post-metadata">

**Author:** ![alexrp](https://ziggit.dev/user_avatar/ziggit.dev/alexrp/32/2793_2.png) [@alexrp](https://ziggit.dev/u/alexrp)\
**Post date:** [October 2, 2026, 5:16pm UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/5 "2026-10-02T17:16:09Z")

</div>

We build LLVM and Zig for 27 platforms for tarballs.

---

<div class="post-metadata">

**Author:** ![yinameah](https://ziggit.dev/user_avatar/ziggit.dev/yinameah/32/8453_2.png) [@yinameah](https://ziggit.dev/u/yinameah)\
**Post date:** [October 2, 2026, 5:28pm UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/6 "2026-10-02T17:28:31Z")

</div>

So it’s really just 20 hours of compilation ? Gosh, impressive.

So you don’t build every commit in master, right? How do you decide when to update the tarball for the dev version? Is it a manual process?

Anyways, thanks for the amazing job and finger crossed I guess ❤

---

<div class="post-metadata">

**Author:** ![alexrp](https://ziggit.dev/user_avatar/ziggit.dev/alexrp/32/2793_2.png) [@alexrp](https://ziggit.dev/u/alexrp)\
**Post date:** [October 2, 2026, 5:58pm UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/7 "2026-10-02T17:58:24Z")

</div>

The tarballs workflow runs on a cron schedule: [https://codeberg.org/ziglang/ziglang.org/src/commit/69ff592d72305c6f5e6ed59cb677aef0711eb601/.forgejo/workflows/build-tarballs.yml#L5](https://codeberg.org/ziglang/ziglang.org/src/commit/69ff592d72305c6f5e6ed59cb677aef0711eb601/.forgejo/workflows/build-tarballs.yml#L5)

Once run, it picks the most recent green build from ziglang/zig and builds tarballs for that; we don’t build tarballs for every push.

---

<div class="post-metadata">

**Author:** ![nukkeldev](https://ziggit.dev/user_avatar/ziggit.dev/nukkeldev/32/6074_2.png) [@nukkeldev](https://ziggit.dev/u/nukkeldev)\
**Post date:** [October 2, 2026, 8:56pm UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/8 "2026-10-02T20:56:51Z")

</div>

> **[0.17.0 Release Notes ⚡ The Zig Programming Language](https://ziglang.org/download/0.17.0/release-notes.html)**

---

<div class="post-metadata">

**Author:** ![pierrelgol](https://ziggit.dev/user_avatar/ziggit.dev/pierrelgol/32/10233_2.png) [@pierrelgol](https://ziggit.dev/u/pierrelgol)\
**Post date:** [October 2, 2026, 9:30pm UTC](https://ziggit.dev/t/0-17-0-tagged-o/17790/9 "2026-10-02T21:30:05Z")

</div>

> Advanced users can override the cache poisoning behavior with a new CLI option:
> 
> ```zig
> --cache-poison[=mode] Override configuration caching behavior
> pure (default) Avoid false positive cache hits
> poisoned Don't cache the configuration
> disallowed Panics when cache would be poisoned
> ignored A little poison never hurt anybody  
> 
> ```

This is hilarious 😂