Is Open WebUI v0.13.0 safe to update?

Yes, with care. New minor release with database schema changes. Back up your Open WebUI data volume first, and if you run multiple workers or servers, read the migration notes before upgrading.

What users are reporting

3 public report(s) mention this version, none clearly describing breakage. Most-discussed: “feat: upgrade outdated npm packages that artifact scanners block”. Sources: GitHub · checked 2026-11-04

• feat: upgrade outdated npm packages that artifact scanners block (GitHub, closed)
• issue: [regression] [dev] Reason and comment of a thumbs-down rating are lost when saved before tags are generated (GitHub, closed)
• issue: [regression] [dev] Holding Shift no longer shows the Delete buttons on the Notes page after clicking a button (GitHub, closed)

Reports are from public issue trackers and forums. Their count isn't a failure rate, and an empty list doesn't prove an update is safe.

⚠️ What breaks

Nothing explicitly breaking is flagged, but the notes mention migrations, deprecations or larger changes. Most setups upgrade fine. Back up first and update when you have time to check.

From the release notes

• New major/minor line (v0.13.0): larger changes than a patch release.
• ⚠️ **Database Migrations**: This release includes database schema changes; we strongly recommend backing up your database and all associated data before upgrading in production environments. If you are running a multi-worker, multi-server,

Read the full official release notes →

✅ What to do first

1. Read the official release notes (linked in “What breaks”).
2. Back up config and data (snapshot the VM/volume if you can).
3. Note the version you are on now, so you can roll back.
4. Update, then check logs and core functions before walking away.

↩️ How to roll back to v0.12.5

Docker: snapshot/back up the data volumes first, then if needed change the tag back, e.g. image: ghcr.io/open-webui/open-webui:v0.12.5, and run docker compose up -d. Tag format varies by image (some drop the “v”), so check the registry’s tag list.