---
title: "v1.91.4 - Docker Migration Assets & Prisma Bake"
url: "/release_notes/v1.91.4/v1-91-4"
canonical_url: "https://docs.litellm.ai/release_notes/v1.91.4/v1-91-4"
type: "release-notes"
last_updated: "2026-10-08"
related:
  - "/release_notes/v1.92.0/v1-92-0"
  - "/release_notes/v1.91.3/v1-91-3"
---
# v1.91.4 - Docker Migration Assets & Prisma Bake

> Index of all LiteLLM docs: https://docs.litellm.ai/llms.txt

## Deploy this version

**Docker**

```bash
docker run \
-e STORE_MODEL_IN_DB=True \
-p 4000:4000 \
docker.litellm.ai/berriai/litellm:1.91.4
```

**Pip**

```bash
pip install litellm==1.91.4
```

`v1.91.4` is a patch release on top of [`v1.91.3`](/release_notes/v1.91.3/v1-91-3). It backports two Docker fixes onto the 1.91.x line. The first restores the `/app/litellm-proxy-extras` source directory in the runtime images, so downstream migration jobs that point `prisma migrate deploy` at that path apply migrations again instead of silently succeeding with no schema. The second bakes the prisma CLI and engines at `/opt/prisma`, a fixed path every runtime uid can read, so fresh-database migrations work under kubernetes `runAsUser`, `docker --user`, and other non-root deployments with no network access. The release also carries routine dependency maintenance updates to mcp and soupsieve in the image lockfile.

### What's Changed

- fix(docker): restore litellm-proxy-extras source dir in runtime images - [PR #33592](https://github.com/BerriAI/litellm/pull/33592)
- fix(docker): bake prisma CLI and engines at a fixed path so fresh-DB migrations work for any uid offline - [PR #33853](https://github.com/BerriAI/litellm/pull/33853)

## Full Changelog

https://github.com/BerriAI/litellm/compare/v1.91.3...v1.91.4

## Related pages

- [v1.92.0](https://docs.litellm.ai/release_notes/v1.92.0/v1-92-0.md)
- [v1.91.3](https://docs.litellm.ai/release_notes/v1.91.3/v1-91-3.md)
