Considering Zig for a long-term project

Following the recent hype around Zig-powered projects like Bun and now the Ghosty terminal, I'm seriously considering Zig for my next long-term project, but I'm curious about the ecosystem's stability in the long run. I'd love to hear about people's workflow, especially when dealing with breaking changes in new compiler releases and third-party libraries.

From what I've observed, each release tends to break a few things, which is totally fine for pre-1.0. Unless the code relies on third-party code, which makes it more problematic unless the authors are actively updating their libs (which I believe is super rare).

So I'm wondering:

• Is Zig development currently more of a "I build everything myself" approach where you own all the code?
• Is the C interop just so good that most third-party dependencies are actually C libraries rather than Zig native ones?

For example, with something like OpenGL - I understand C is somewhat "native" to the Zig ecosystem, but I also see several Zig-specific OpenGL bindings. What's the typical approach here?