# Anyone unable to upgrade to 0.17.0 for some reason?

**URL:** <https://ziggit.dev/t/anyone-unable-to-upgrade-to-0-17-0-for-some-reason/17912>\
**Category:** Help\
**Tags:** zig-0-17\
**Created:** [October 10, 2026, 6:26pm UTC](https://ziggit.dev/t/anyone-unable-to-upgrade-to-0-17-0-for-some-reason/17912 "2026-10-10T18:26:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrewrk](https://ziggit.dev/user_avatar/ziggit.dev/andrewrk/32/7011_2.png) [@andrewrk](https://ziggit.dev/u/andrewrk)\
**Post date:** [October 10, 2026, 6:26pm UTC](https://ziggit.dev/t/anyone-unable-to-upgrade-to-0-17-0-for-some-reason/17912/1 "2026-10-10T18:26:43Z")

</div>

Anyone who ran into regressions or other blockers when upgrading to 0.17.0, is your bug filed, and assigned to the 0.17.1 milestone? Anyone need help upgrading?

---

<div class="post-metadata">

**Author:** ![flow](https://ziggit.dev/letter_avatar_proxy/v4/letter/f/8edcca/32.png) [@flow](https://ziggit.dev/u/flow)\
**Post date:** [October 11, 2026, 5:27pm UTC](https://ziggit.dev/t/anyone-unable-to-upgrade-to-0-17-0-for-some-reason/17912/2 "2026-10-11T17:27:57Z")

</div>

Waiting for projects like dvui to upgrade first.

---

<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 11, 2026, 6:37pm UTC](https://ziggit.dev/t/anyone-unable-to-upgrade-to-0-17-0-for-some-reason/17912/3 "2026-10-11T18:37:02Z")

</div>

DVUI 0.17.x branch is almost merged state.

Now would be the perfect time to test your project against it.

There is something wrong with -fincremental, **sdl2** backend that I didn’t have time to investigate but that’s the only issue I encountered and all other backends compile incrementally as far as I can tell. (i.e. on my machine 😁)

Which is crazy cool btw. Display the window on screen is an order of magnitude (!) slower than compile the app. You read that right 😅.

---

<div class="post-metadata">

**Author:** ![Valden](https://ziggit.dev/user_avatar/ziggit.dev/valden/32/4572_2.png) [@Valden](https://ziggit.dev/u/Valden)\
**Post date:** [October 11, 2026, 7:31pm UTC](https://ziggit.dev/t/anyone-unable-to-upgrade-to-0-17-0-for-some-reason/17912/4 "2026-10-11T19:31:03Z")

</div>

Not directly tied to the zig project itself, but the lack of support for zls for the 0.17.0 release forced me to revert back to my previous version that had support for it (0.17.0-dev.2125+0d600e488 in my case).

---

<div class="post-metadata">

**Author:** ![Kaeru](https://ziggit.dev/user_avatar/ziggit.dev/kaeru/32/3335_2.png) [@Kaeru](https://ziggit.dev/u/Kaeru)\
**Post date:** [October 11, 2026, 8:52pm UTC](https://ziggit.dev/t/anyone-unable-to-upgrade-to-0-17-0-for-some-reason/17912/5 "2026-10-11T20:52:24Z")

</div>

I’ve tried updating my project to use Raylib 0.17 but haven’t managed to as I haven’t had much time to dig into the build system issues that have popped up.

I know there was a rework of the build system, with the maker and configurer being separated [0.17.0 Release Notes ⚡ The Zig Programming Language](https://ziglang.org/download/0.17.0/release-notes.html#Separate-the-Maker-Process-from-the-Configurer-Process) but it’s been hard to find information about what those changes entail for those writing libraries and those consuming it.

For raylib-zig in particular, the project is at the 3rd build system patch to figure out how users can consume said library [Unable to find module "raylib," zig 0.17.0 · Issue #364 · raylib-zig/raylib-zig · GitHub](https://github.com/raylib-zig/raylib-zig/issues/364). Personally I’ve had a hard time finding what the issue could be based on the build system documentation (and release notes), so I plan on diving into the code later to understand. In sum, the issue seems to be circling around lazy dependencies and in how 0.17 changed when and how dependencies are fetched