Skip to content

llama.cpp ships v1.0.0 and promises API breaks only in majors

Short answer

The ggml-org team released v1.0.0 of llama.cpp and ggml, the libraries many local AI applications build on. From now on, any API or ABI incompatibility will arrive as a major-version bump. Anyone embedding these libraries can pin versions and read upgrade risk from the number.

What this means for operators

If your sales, support or operations tooling runs a model locally, for example to keep customer data in-house, there is a good chance llama.cpp sits somewhere in that stack, either in your own code or inside a vendor's product. Ask the vendor or your developer which version they ship, and pin your builds to the 1.x line. Treat a jump to 2.x as a planned change with testing, and let minor and patch releases through your normal update routine. The new distribution channels (Docker, Homebrew, Winget and others) also mean fewer custom build scripts to maintain on the machines you control.

The ggml-org team announced llama.cpp v1.0.0 on Hugging Face, releasing the llama.cpp library (libllama) and the underlying ggml tensor library (libggml) as 1.0.0 at the same time. The project is about three and a half years old, and the team says many downstream applications now depend on it.

What the version number now means

The headline change is a commitment about compatibility. Both projects will signal API and ABI incompatibilities through a major-version bump. The team lays out the rules for all its projects that use semantic versioning:

  • Major: a breaking change to the public C API in the include directory.
  • Minor: a backward-compatible feature, backend update, model support or API addition.
  • Patch: a bug fix with no API change.

The team says it will be stricter about making these boundaries visible as adoption grows.

Distribution

The post lists the channels through which the software is distributed:

  • Pre-release artifacts for Linux, macOS, Windows, Android and iOS.
  • Docker images for Linux.
  • Debian packages.
  • Homebrew for macOS and Linux.
  • conda-forge for Windows, macOS and Linux.
  • MacPorts and Winget.
  • An XCFramework for iOS and macOS.

The team also points packagers to a discussion thread on how to add the projects to their own release pipelines.

Development and coverage

The team says it uses LLMs in its own development in a measured way, while keeping control of the architecture. It is investing in CI infrastructure, using Hugging Face's HF Buckets and HF Jobs for capacity, and adding self-hosted runners across major hardware platforms with support from NVIDIA, AMD, Qualcomm, Arm, IBM and Intel.

On models, llama.cpp currently supports more than 150 architecture variants and all mainstream speculative decoding methods. Hardware support comes through ggml backends, each of which can be compiled as a dynamic library and loaded at runtime.

What is not in the announcement

The post does not describe new model capabilities or performance figures, and it gives no timeline for a future major release. The change is about predictability for the people who build on the libraries.

Source: Hugging Face · In the Atlas: Hugging Face →

The tools in this story

  • NVIDIA - price, who uses it, alternatives
Next step

Visibility Analyzer

An AI news item will not tell you how assistants see your own site. The Visibility Analyzer checks that on your live site: which answers cite you, which pages an engine cannot retrieve, and what to fix first. Free to run.

Run a free visibility audit

Free to run. No card.

Fee
Free
Length
One run, minutes

Free tier: two analyses a day, no card required.