●Change8

Migrating to LocalAI v2.29.0

Version v2.29.0 introduces 3 breaking changes. This guide details how to update your code.

Released: 5/12/2025

3
Breaking Changes
3
Migration Steps
1
Affected Symbols

⚠️ Check Your Code

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

AutoGPTQ backend

Breaking Changes

●Issue #1

Container images containing extra Python dependencies (like those for `diffusers`) now require the \`-extras\` suffix (e.g., \`latest-gpu-nvidia-cuda-12-extras\`). Default images are now slimmer and do not include these dependencies.

●Issue #2

The separate \`-ffmpeg\` container image tags have been removed because FFmpeg is now included in all core images. Users should switch to the corresponding base image tag (e.g., \`latest-gpu-hipblas-ffmpeg\` becomes \`latest-gpu-hipblas\`).

●Issue #3

The AutoGPTQ backend has been dropped because it was discontinued upstream.

Migration Steps

  1. 1
    If you relied on extra Python dependencies (like diffusers) in your container, update your image pull command to use the new \`-extras\` suffix (e.g., change \`latest-gpu-nvidia-cuda-12\` to \`latest-gpu-nvidia-cuda-12-extras\` if you need those dependencies).
  2. 2
    If you were using an image tag ending in \`-ffmpeg\`, remove \`-ffmpeg\` from the tag (e.g., change \`latest-gpu-hipblas-ffmpeg\` to \`latest-gpu-hipblas\`).
  3. 3
    If you were using the AutoGPTQ backend, you must switch to an alternative backend as it has been removed.

Release Summary

LocalAI v2.29.0 introduces a major overhaul to container images, slimming down defaults and introducing an \`-extras\` suffix for optional dependencies, alongside new model support and experimental video generation capabilities.

Need More Details?

View the full release notes and all changes for LocalAI v2.29.0.

View Full Changelog