llama.cpp and ggml reach v1.0.0 on 13 November 2026: what the semver rule covers, what actually broke, and where the 1.0 libraries ship
llama.cpp and ggml reached v1.0.0 on 13 November 2026, and the ggml‑org release post frames the milestone as a versioning commitment rather than a feature dump: from here on, both projects say they will express API and ABI incompatibilities through major‑version bumps. The rules are narrow — MAJOR means a breaking change to the public C API under ./include, MINOR covers backward‑compatible features, backend updates, model support or API additions, and PATCH is a bug fix with no API change. The versioned surfaces are libllama, with headers in llama.cpp/include/, and libggml, with headers in ggml/include/. 1.0.0 is itself the first breaking release under that rule. llama.h drops llama_set_warmup, the 35 functions marked deprecated, the defrag_thold field and the --defrag‑thold option, while the NextN/speculative API moves out of llama‑ext.h into llama.h and llama_set_embd_state_src becomes llama_set_ctx_state_src. ggml 1.0.0 prunes its deprecated public API, removes the legacy DIAG_MASK ops and bumps the RPC protocol to v9, which rejects incompatible peers. Two boundaries matter most for integrators. First, the promise as written covers the C headers only: clip.h was removed, mtmd headers changed, server endpoints and CLI flags changed, and stricter GGUF load requirements arrived — none of which a captured source places under the guarantee. Second, channel availability is not uniform. Homebrew's core formula reports stable 1.0.0 with prebuilt bottles, while conda‑forge still serves build‑numbered packages rather than the 1.0.0 tag. Docker, Debian, MacPorts and Winget were not verified, and post‑1.0.0 fixes so far exist only in nightly pre‑releases.
A stability commitment stated for what comes next
The bump rules, in full
The post states that the following rules apply to all ggml‑org projects using semantic versioning 1:
- MAJOR — a breaking change to the public C API in ./include.
- MINOR — a backward‑compatible feature, backend updates, model support, or an API addition.
- PATCH — a bug fix with no API change.
The scope is tighter than the headline commitment. The MAJOR row is written around the public C API in ./include; ABI appears in the prose sentence above the table, not inside the table row itself. The table also names only the two libraries above — mtmd and the other components this release touches are not listed there 1.
What 1.0.0 itself removed
The 1.0.0 tag also bundles additive work
Where the promise stops
Several surfaces changed at 1.0.0 without a stated guarantee:
- mtmd headers. The versioned‑releases table lists libllama and libggml only, yet this release removes clip.h and changes mtmd.h and mtmd‑helper.h 1 2. No retained source says whether mtmd carries the same promise.
- The server and CLI. --defrag‑thold was removed in this bump and server endpoints changed, but the rules table scopes a major bump to the public C API in ./include. Nothing captured states a compatibility rule for the HTTP API, CLI flags or the bundled web UI 1 2. One review comment notes that a router preset which still sets defrag‑thold will now stop the router at startup, because the router refuses unknown keys 6.
- GGUF model files. 1.0.0 adds load‑time requirements, including requiring the projector and patch‑embedding tensors, a 2x2 spatial merge for some projectors, and an F32 position embedding for HunyuanVL 2. Those can affect older model files, and no captured text states a file‑format compatibility policy.
- Support duration. No source in this package commits to a maintenance window for the 1.x line.
One further limit: the itemized list of the 35 removed functions is not in the retained evidence, because it sits in the #30565 diff, which this capture does not include 6.
Getting the 1.0 libraries today
The post names the channels and the platforms each one targets 1:
- Pre‑release artifacts — Linux, macOS, Windows, Android, iOS
- Docker — Linux
- Debian — Linux
- Homebrew — macOS, Linux
- conda‑forge — Windows, macOS, Linux
- MacPorts — macOS
- Winget — Windows
- XCFramework — iOS, macOS
Checked after the announcement, two of those channels differ from each other:
- Homebrew carries 1.0.0. The homebrew/core formula reports stable 1.0.0, pinned to tag v1.0.0 at revision b1b770d90d94cad9e9ea5b993bdbc383a522fb28, with prebuilt bottles for arm64 macOS (golden_gate, tahoe, sequoia), arm64_linux and x86_64_linux 7. It depends on a separate ggml formula plus openssl@4, and that formula's version was not captured — so this record does not establish which libggml Homebrew delivers 7.
- conda‑forge does not. Its llama.cpp package reports latest_version 12418 across linux‑64, linux‑aarch64, win‑64, osx‑64 and osx‑arm64, last modified 15 November 2026 — a build‑number style version rather than the 1.0.0 tag 8. Reading 12418 as a specific nightly build is inference from naming convention, not a captured statement.
Docker, Debian, MacPorts and Winget were not verified in this package, so 1.0.0 availability there is unknown rather than absent. The blog also links a discussion for packagers on adding ggml‑org projects to packaging and release pipelines, without showing package names 1.
v1.0.0 remains the latest stable tag in both repositories, and post‑tag work lands in nightly pre‑releases; the llama.cpp releases page listed builds b12427 through b12441 for 15–16 November 2026 4 5. Those nightlies carry fixes for problems observed after the tag, including a CUDA MUL_MAT_ID abort with odd src0 columns on AMD hardware (b12433) and an MoE regression on HIP (b12430) 4. Whether the underlying issues also affect the v1.0.0 tag is not established by the retained text, so treat that as a possibility to check rather than a fact.