Releases
Open Chat Interface's releases, what to expect before 1.0, and how releases are published.
| Release | Date | In short |
|---|---|---|
| v0.10.2 | 2026-10-03 | One send starts one conversation; a limit on starting conversations; unused conversations cleaned up after a day. No migrations. Use this instead of v0.10.1. |
| v0.10.1 | 2026-10-03 | One block for the model's work: a reply's reasoning and tool steps in one collapsible block, artifact cards and approvals kept in sight below it, artifact details inside the card. No migrations. |
| v0.10.0 | 2026-10-03 | Finish and harden: your shared links, a default model per person, optional self-service account deletion, Delete user, backups that copy files, legal hold over every deletion, deletions in the compliance export, a fallback search provider, PDF export in every script, a resizable artifact panel, branding everywhere. Migrations 0035 to 0038, all pre-deploy safe. |
| v0.9.2 | 2026-10-03 | Security: the API trusts one client address, set by the web container; TRUSTED_PROXIES for proxies in front of it. No migrations. |
| v0.9.1 | 2026-10-03 | No published images; use v0.9.2. Project conversations under their project in the sidebar; Settings → Account works (password, devices, name); a settings review. No migrations. |
| v0.9.0 | 2026-10-03 | Make and operate: artifacts, export as Word, PDF, PowerPoint and Excel, user memory, long conversations summarised, meaning-based project search and reranking, compliance export and legal hold, automated backups, metrics, traces and webhooks. |
| v0.8.0 | 2026-10-02 | Tools and connected knowledge: tool calling with approvals, web search as a tool, search over large project files, MCP connectors with per-person OAuth. |
| v0.7.0 | 2026-10-01 | Organise and find: per-role features, full-text conversation search, projects, Mermaid diagrams, switching between retried replies, export everything and import from ChatGPT or Claude. |
| v0.6.1 and earlier | 2026-08-07 to 2026-10-01 | From the first release to guided setup and the Roles & access page. |
The full list of changes is in the changelog.
Before 1.0
OCI follows semantic versioning, but before 1.0 a minor release may change behaviour; its notes say how to adapt.
- Upgrades are forward-only. Migrations cannot be undone by reverting images; downgrading past a migration means restoring a backup. Read every release's upgrade notes between your version and the target. See Upgrades.
- The API and web images are a pair. Deploy both from the same release.
- There is no public API. The HTTP API serves OCI's own web app and may change in any release. A personal-key API is not planned.
What's next
The roadmap is a plan, not a promise:
- Now, v0.11, always on: upgrading from the previous minor release with no downtime on large deployments, surviving a database failover partway through, and tested rather than promised. Planned: two-phase and lock-safe migrations, rolling-upgrade tests and an upgrade preflight, a scale test harness, connection pooling, a Kubernetes Helm chart,
linux/arm64images, draining replies on shutdown and a separate worker role. - Later, v1.0 and beyond: assistants, code execution, deep research, image generation, voice, groups and finer roles, multi-factor authentication and interface translations.
How releases are published
- The container images are the release artifacts:
ghcr.io/ncecere/open-chat-interface/apiandghcr.io/ncecere/open-chat-interface/web, forlinux/amd64. - Each stable release is tagged
vX.Y.Z.latestmoves to the newest stable release once both images are published; use it only for evaluation. - Images are built and published by CI from the release tag, after checks.
- Releases before v0.5.0 were first published to an earlier registry and may not be on GHCR.