Change8

Migrating to LocalAI v4.3.0

Version v4.3.0 introduces 2 breaking changes. This guide details how to update your code.

Released: 5/24/2026

2
Breaking Changes
3
Migration Steps
9
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

pkg/oci/cosignverifygrpc-server.cppModelLoader.LoadSmartRouter.RoutePickBestReplicaprobeHealthusage_recordsGET /api/auth/usage/sourcesGET /api/auth/admin/usage/sources

Breaking Changes

Issue #1

Enabling strict backend integrity checking via `--require-backend-integrity` or `LOCALAI_REQUIRE_BACKEND_INTEGRITY=true` will now cause a hard-fail if a backend image lacks the required policy or SHA256 digest, whereas previously it might have only warned.

Issue #2

In Distributed Mode, model loading logic was changed to ensure per-request routing across replicas. If custom logic relied on the previous behavior where the first request pinned subsequent traffic to that node, that behavior is now broken, and traffic should be correctly load-balanced across available replicas.

Migration Steps

  1. 1
    If you rely on strict backend integrity, enable `--require-backend-integrity` or set `LOCALAI_REQUIRE_BACKEND_INTEGRITY=true` and ensure your gallery YAML includes the necessary `verification:` block.
  2. 2
    If you experience unexpected load balancing behavior in Distributed Mode, review your configuration as per-request replica routing is now enforced.
  3. 3
    If you need to disable the new default prompt caching for llama.cpp models, set `prompt_cache_all: false` or use `options: ["kv_unified:false"]` in your model YAML.

Release Summary

LocalAI 4.3.0 hardens security with keyless cosign signatures for backend images and significantly improves performance by enabling the llama-cpp prompt cache by default. This release also introduces detailed per-API-key usage tracking and major stability improvements for Distributed Mode.

Need More Details?

View the full release notes and all changes for LocalAI v4.3.0.

View Full Changelog