# ggml

llama.cpp and its underlying tensor library ggml both reach v1.0.0, tying semantic versioning to the public C interface: a major bump marks a breaking change to the public C API under ./include, a minor bump covers backward-compatible features, backend updates, model support or API additions, and a patch covers bug fixes with no API change. After 3.5 years of adoption, interface stability becomes the point of release management, a promise earlier version numbers did not carry.

llama.cpp and its underlying tensor library ggml both reach v1.0.0, tying semantic versioning to the public C interface: a major bump marks a breaking change to the public C API under ./include, a minor bump covers backward-compatible features, backend updates, model support or API additions, and a patch covers bug fixes with no API change. After 3.5 years of adoption, interface stability becomes the point of release management, a promise earlier version numbers did not carry.

llama.cpp released libraries v1.0.0, tying major version numbers to API and ABI incompatibilities so downstream applications that depend on its library interfaces get a predictable upgrade boundary. The project has accumulated many downstream dependents since it began, and interface stability had not previously been promised through version numbering. The new rule applies to all ggml-org projects that use semantic versioning, and both llama.cpp and ggml will now reflect incompatible changes in major version bumps.

llama.cpp released libraries v1.0.0, tying major version numbers to API and ABI incompatibilities so downstream applications that depend on its library interfaces get a predictable upgrade boundary. The project has accumulated many downstream dependents since it began, and interface stability had not previously been promised through version numbering. The new rule applies to all ggml-org projects that use semantic versioning, and both llama.cpp and ggml will now reflect incompatible changes in major version bumps.