●Change8

Migrating to LocalAI v3.3.1

Version v3.3.1 introduces 1 breaking change. This guide details how to update your code.

Released: 8/1/2025

1
Breaking Changes
2
Migration Steps
6
Affected Symbols

⚠️ Check Your Code

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

localai/localai:latest-gpu-intel-f32localai/localai:latest-gpu-intel-f16localai/localai:latest-aio-gpu-intel-f32localai/localai:latest-aio-gpu-intel-f16flux.1-kontext-devstablediffusion-ggml

Breaking Changes

●Issue #1

Intel GPU container images have been renamed. \`latest-gpu-intel-f32\` and \`latest-gpu-intel-f16\` are replaced by a single image: \`latest-gpu-intel\`. For AIO images, \`latest-aio-gpu-intel-f32\` and \`latest-aio-gpu-intel-f16\` are replaced by \`latest-aio-gpu-intel\`.

Migration Steps

  1. 1
    If you were using the old Intel GPU image tags, update your Docker run commands to use the new unified tag: \`localai/localai:latest-gpu-intel\` (or \`localai/localai:latest-aio-gpu-intel\` for AIO).
  2. 2
    To use Flux Kontext image editing, install the model using \`local-ai run flux.1-kontext-dev\`.

Release Summary

This minor release introduces support for Flux Kontext and Flux krea for image editing and generation. It also resolves critical bugs related to Intel GPU images and renames the corresponding container image tags.

Need More Details?

View the full release notes and all changes for LocalAI v3.3.1.

View Full Changelog