we_are_coded.by CODE · The world, decoded
БГ

llama.cpp · Builders

llama.cpp and ggml reach 1.0.0: a broken API will now show up in the major version

On 13 November ggml-org released libllama and libggml 1.0.0. From here on, every incompatibility in the public C API and in the ABI bumps the major version, so anyone who built a local model into an app can read the number as a warning.

Source
ggml-org (Hugging Face)
Published
The event
Checked on
Responsible editor
Cvetelin Ivanov
How we work
MethodCorrections

The version number is now a promise. On 13 November ggml-org released libllama and libggml 1.0.0 and wrote down plainly what each change of the number will mean. If you built llama.cpp into an app, that is the most useful line in the whole post.

Fact

The facts: on 13 November 2026 the ggml-org team published on its Hugging Face blog that llama.cpp v1.0.0 (libllama) and ggml v1.0.0 (libggml) are out. The promise: moving forward, both llama.cpp and ggml will reflect API and ABI incompatibilities with major-version bumps. The rules the team gives for all its projects that use semantic versioning: MAJOR for a breaking change to the public C API in ./include; MINOR for a backward-compatible feature, backend update, model support or API addition; PATCH for a bug fix with no API change. According to the team, the project is 3.5 years old, supports more than 150 architecture variants and all mainstream speculative decoding methods, and many downstream applications already depend on it. Distribution runs through Docker, Debian, Homebrew, conda-forge, MacPorts, Winget, XCFramework and pre-release artifacts for Linux, macOS, Windows, Android and iOS. For its CI, the team has hardware support from NVIDIA, AMD, Qualcomm, Arm, IBM and Intel.

Read the table as a contract. When the major version moves, something in the public C API broke and your build may not compile. When the minor or the patch moves, by the team's rules your code should not be affected: a new backend, a new model or a fix. That gives you the right to read the number before you read the release notes.

One thing is left unsaid. The table speaks about the public C API in the include folder. The ABI is mentioned in the promise, but the page gives no separate rule for it. If you link the library dynamically, find out what exactly it covers before you rely on it.

The major version is now a warning.

The reason is dependency. The team says many applications already depend on the project and every new integration means more developers relying on its interfaces. There are no new models here and no new speed. The news is the contract.

Check which version of libllama is wired into your project. If it is pinned to a commit, not to a version, 1.0.0 is a reason to change that.

The visual is generated code-art, no third-party images.