What changed
The ggml-org maintainers released libllama and libggml 1.0.0 and adopted semantic-version rules for their public C headers. Major versions now signal breaking public-API changes, while minor and patch releases distinguish compatible additions from fixes.
Why it matters
Local-inference applications depend on fast-moving native libraries whose unmarked interface changes can break builds or runtime integrations. A versioned compatibility contract makes upgrade policy, dependency pinning and downstream support more inspectable.
What to do
Pin the 1.0 libraries in a staging build, compile every downstream binding against the published headers, run fixed output and performance tests across target backends, and document the major-version gate before updating production packages.
Caveat
Semantic versioning covers the stated public C API, not model-output parity, numerical behavior, performance or every internal interface. The project still publishes rapid prereleases, and downstream bindings may impose their own compatibility constraints.