All News
llama-cppggmlapi-stabilitylocal-llmsemver

llama.cpp v1.0.0 deletes 35 functions to promise a stable C API

llama.cpp tagged v1.0.0 on 13 November. The release deletes 35 deprecated functions and promises a stable C API, a narrower contract than most users assume.

Vlad MakarovVlad Makarovreviewed and published
6 min read
llama.cpp v1.0.0 deletes 35 functions to promise a stable C API

llama.cpp tagged v1.0.0 on 13 November, closing a 0.x series that ran from v0.1.0 to v0.9.0 this autumn in a project that spent the first three and a half years of its life shipping daily build tags instead. The release notes are mostly a feature list: FP8 KV caches, a MoE expert cache promoted into the public header, three new text architectures, an OpenAI-compatible audio endpoint. The version number is the part that changes how applications consume the library. In the Hugging Face announcement, the maintainers write that "both llama.cpp and ggml will reflect API and ABI incompatibilities with major-version bumps," which turns a number into a contract. Paying for it required deleting 35 deprecated functions in one release.

What the number promises

The scheme is ordinary semver, applied to an unusual project. The tags it replaced were already numbered: v0.6.0 landed in early October, three tags before this one. From now on the first digit moves only when the public C API in the ./include directory breaks, and anything that adds a model architecture, updates a backend or extends the API is a minor bump.

BumpWhat it now marks
MAJORBreaking change to the public C API in ./include
MINORBackward-compatible feature, backend update, model support, API addition
PATCHBug fix with no API change

Read the middle row twice. Model support is a minor change, and model support is what llama.cpp does most weeks. The promise does not slow down architecture churn, it slow-walks one directory: the C surface that downstream applications link against.

The deletions are the release

The removals are the substance. llama_set_warmup is gone, the release deletes 35 deprecated functions in one cut, and defrag_thold and the --defrag-thold flag go with them (PR #30565). The NextN and speculative decoding API moves out of llama-ext.h and into llama.h, so a surface that lived outside the stable header is now inside it. llama_set_embd_state_src is renamed llama_set_ctx_state_src.

None of that is free. Anyone who built against the deleted symbols gets a compile error, and that is the intended cost of a major bump: the cleanup happens once, behind a number that tells a packager to expect it. Steady-state users of the CLI and the server lose nothing, because the flag that disappeared, --defrag-thold, was never part of the C API promise in the first place.

What rides along

The features are real and mostly downstream of work already merged. FP8 KV caches arrive through -ctk and -ctv set to f8_e4m3, with optional static per-tensor scales (PR #28392). The MoE expert cache that we covered when it gained a CPU-share dial is now public: moe_cache_size and moe_cache_cpu_share join llama_context_params (PR #30966), with LRFU and ClassLRU replacement, no CPU wait on cached experts, and misses routed to host memory in proportion to that share (PRs #31233, #31888).

External PLE and engram tensors can now load from separate GGUF shards through --shard and --ple (PR #31185), and Windows gets unbuffered model loading that mirrors the Linux DirectIO path (PR #26014). Three text architectures land: Kimi-K3.1-Pro, which is K3 with the full-attention MLA layers replaced by DSA; Ripple-65B-Preview from ricursive, a dense 65B design the notes say needs no new operations; and xing4_0, which mixes mHC, MLA, MoE and multi-token prediction. drama-3 TTS from fishaudio, MageVL-Cowork and Kimi-K3.1 vision fill out the multimodal side.

Most of the server work is hardening: fixes for SSRF, CORS and DNS rebinding, MCP tool cancellation, a redesigned web UI with chat groups and a markdown editor, and the new /v1/audio/speech route that makes the TTS work reachable over HTTP.

The contract is narrower than the dependency

Here is the tension worth naming. The guarantee covers the C API in ./include. What most people actually depend on is not that: it is the CLI flags, the server's HTTP schema, and the GGUF file format. None of those three appears in the versioning rules. This very release proves the point by removing --defrag-thold from the command line while calling the change part of a clean major bump, which is fine under the scheme and disruptive for anyone with a systemd unit or a launch script. As written, the rules do not mention GGUF versions or CLI flags at all, so a change to either would not require a major bump.

The Reddit thread on r/LocalLLaMA made the same objection within hours. OsmanthusBloom wrote: "I'm a little confused about the rules for major/minor/patch releases. You list only changes in the C API as a reason for a major version. But I believe there are relatively few programs that depend on the C API." The counter-reading in the same thread was blunter, from Large_Yams: "Basically you've been downloading v0.1.12360. This is now v1.0.0."

Both are correct about different things. For a person running llama-server on a workstation, v1.0.0 is a renumbering with a changelog attached.

Reception and what to watch

The version bumped ggml to v1.0.0 as well, which matters because the two libraries version together. The Hugging Face post dates the inception commit three and a half years back, long enough that most of the project's history was spent on build tags like b12387 rather than on releases. The project now claims more than 150 architecture variants and every mainstream speculative decoding method, and it ships pre-release binaries for Linux, macOS, Windows, Android and iOS, plus Docker, Debian, Homebrew, conda-forge, MacPorts, Winget and an XCFramework. That distribution list is the real measure of how many things a breaking change can reach.

Reception was measurable but modest. The release page shows 112 people reacting, the Hugging Face post drew 168 upvotes, and the Reddit thread reached 1,625 points and 194 comments. On Hacker News the largest submission, headlined around a native macOS app, sat at 25 points and 4 comments.

Whether the promise holds is testable and will be tested soon, because the minor-bump escape hatch covers exactly the churn this project generates fastest. Watch for a MAJOR tag that ships without a deletion in ./include, or a MINOR one that quietly breaks a build. In the meantime, the releases page still lists mostly per-build tags, and for the people who pin those, nothing about this week changed except the number at the end.

Related Articles

Scroll down

to load the next article