llama.cpp Reaches v1.0.0, Promising a Stable API for Local AI
llama.cpp v1.0.0 is now available
Context
A 1.0 release means downstream apps can depend on a stable llama.cpp and ggml API, with major version bumps when that API breaks.
Georgi Gerganov, the creator of llama.cpp, posted on November 13 that llama.cpp v1.0.0 is now available, and linked to a Hugging Face blog post by the ggml org team. The blog says the 1.0.0 release covers both the llama.cpp inference library and the ggml tensor library, and that future major version bumps will mark incompatible changes to the public C API. The project has been used for local and private model inference for about three and a half years.
Deep dive
Georgi Gerganov posted on November 13 that llama.cpp v1.0.0 is now available, and linked to a Hugging Face blog post titled llama.cpp v1.0.0 : A stronger foundation for the local AI ecosystem. The blog, published the same day by the ggml org team, says the release highlights the project's responsibility to downstream developers who depend on its library interfaces.
According to the post, the 1.0.0 milestone applies to both llama.cpp, the C and C++ library for LLM inference (libllama), and ggml, the tensor library (libggml). Going forward, the team says both projects will use semantic versioning: a major version bump for a breaking change to the public C API in the include headers, a minor bump for backward compatible features or API additions, and a patch bump for bug fixes with no API change.
The blog says the project began about three and a half years ago and that llama.cpp currently supports more than 150 architecture variants as well as mainstream speculative decoding methods. It also lists distribution channels including Docker, Debian, Homebrew, conda forge, MacPorts, Winget and an XCFramework for iOS and macOS, and says hardware support for CI runners comes from NVIDIA, AMD, Qualcomm, Arm, IBM and Intel.
What to expect next
Watch the project's release notes and packaging channels for how strictly the new versioning is applied, and whether downstream apps start pinning to the 1.0 API. Follow up posts may cover desktop apps or additional backends. Independent packagers will show how quickly v1.0.0 lands in Homebrew, Debian, Docker and other channels named in the blog. If a later release has to bump the major version, that will test the new contract.