ggerganov/llama.cpp
b12131Curated ai tools / local-ai / runtime repository (ggerganov/llama.cpp) tracked via conditional GitHub .atom polling.
@ggerganov/llama.cpp is an open-source library and developer tool in the ggerganov/llama.cpp ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.
Ships @ggerganov/llama.cpp@b12131 with upstream runtime. Drop-in upgrade. Migration: None.
Key Release Highlights (b12131)
- Ships
@ggerganov/llama.cpp@b12131with upstream runtime refinements and stability fixes fromggerganov/llama.cpp. - Updates TypeScript declarations and internal module exports for
b12131.
Verified safe drop-in upgrade for @ggerganov/llama.cpp in package.json.
npm install @ggerganov/llama.cpp@b12131Ecosystem Compatibility Matrix & Verified Graph Warnings
Zero-Noise Historical Release Timeline (1)
Format: [Core Change] + [Required Action] + [Migration Effort]Ships @ggerganov/llama.cpp@b12131 with upstream runtime. Drop-in upgrade. Migration: None.
Upgrade & Migration Q&A (ggerganov/llama.cpp b12131)
Direct Answers for Engineers & AI AgentsIs ggerganov/llama.cpp b12131 safe to upgrade in production?
ggerganov/llama.cpp b12131 is classified as COMPATIBLE (MINOR release). Ships @ggerganov/llama.cpp@b12131 with upstream runtime. Drop-in upgrade. Migration: None.
What breaking changes or compatibility risks exist in ggerganov/llama.cpp b12131?
No breaking API changes or peer dependency conflicts are recorded for ggerganov/llama.cpp b12131 in the RepoSense compatibility graph.
What is the bundle size impact of @ggerganov/llama.cpp b12131?
Measured bundle size telemetry is currently unavailable for @ggerganov/llama.cpp b12131; verify build output locally before deploying.
How do I upgrade @ggerganov/llama.cpp to b12131?
Upgrade @ggerganov/llama.cpp to b12131 by running "npm install @ggerganov/llama.cpp@b12131" and applying the migration steps: npm install @ggerganov/llama.cpp@b12131