AIToday
Large Language ModelsAI Coding AssistantsOpen-Source AIAI WeeklyPublished: Nov 14, 2026, 10:00 JST

llama.cpp v1.0.0 lands with semver pledge, 150+ architectures

Send on LINE
llama.cpp v1.0.0 lands with semver pledge, 150+ architectures

3 Key Points

  1. What happened

    Hugging Face's ggml-org team shipped llama.cpp v1.0.0 and ggml v1.0.0 on November 13, 2026, with MAJOR bumps now reserved for breaking C API changes, MINOR for backward-compatible features, PATCH for bug fixes.

  2. Why it matters

    Maintainers say they will be stricter about making version boundaries visible to downstream consumers as adoption grows, giving teams that build on the libraries a clearer signal of when upgrades may break their code.

WHO IT HITSTeams building private or cross-platform AI products on llama.cpp, and the downstream packagers and distributors who ship it, gain a formal version contract for planning upgrades.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The 1.0.0 tag formalizes a relationship that had been informal for years. The team describes the milestone as arriving 3.5 years since llama.cpp's inception, and the release post pairs it with a promise: both llama.cpp and ggml will reflect API and ABI incompatibilities with major-version bumps. For a project whose audience increasingly builds products on top of it, that is a shift from moving-target codebase to versioned dependency.

The release also sketches the project's reach. Beyond more than 150 architecture variants and all mainstream speculative decoding methods, the post lists pre-release artifacts across five operating systems and packaging through seven channels, from Docker to an XCFramework. Hardware vendors contributing self-hosted CI runners — NVIDIA, AMD, Qualcomm, Arm, IBM and Intel — suggest the testing load is distributed across the very vendors whose chips the library targets, with scaling handled by HF Buckets and HF Jobs.

The maintainers frame their priorities as maintaining a high quality codebase, staying in control of the architecture and understanding the implementation details, pitching the result as the most lightweight, versatile and sensible platform for building cross-platform and private AI products. The release also credits six named Hugging Face authors and 104 additional supporters, and lands against a steady run of 138 inference stories tracked in the feed over the past 90 days — a reminder of how crowded the inference-tooling space has become.

FAQ
What do the version numbers mean now?
A MAJOR bump signals a breaking change to the public C API in ./include. MINOR covers backward-compatible features, backend updates and new model support, and PATCH is reserved for bug fixes with no API change.
Which hardware vendors contribute CI runners?
NVIDIA, AMD, Qualcomm, Arm, IBM and Intel provide self-hosted CI runners, with scaling handled by HF Buckets and HF Jobs.
Who authored the release?
The post names six Hugging Face authors — julien-c, ggerganov, clem, pcuenq, raunoryys and nisbenz — alongside 104 additional supporters from the contributor community.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGS Caltex automates Canvas-to-Pipelines handoff, cuts deployment to hours