Skip to main content
Opik Documentation

Search documentation

Type to search this documentation.

On this pageOverview

Self-host changelog

This page only lists breaking and critical changes that affect self-hosted Opik deployments. For the complete list of product updates, see the product changelog.

Opik 2.0 organizes all data around projects. Data created on Opik 1.x — datasets, prompts, experiments, optimizations, automation rules, and alerts — is not visible in the Opik 2.0 UI until you run the background migration jobs that assign each item to a project. Follow the Opik 2.0 migration guide for the step-by-step instructions, including the required job order and the database backups to take first.

  • Updated port mapping when using opik.sh - This may affect existing deployments
  • Fixed persistence when using Docker compose deployments - Requires reconfiguration for existing deployments
  • Updated Dockerfiles to ensure all containers run as non root users - This is a security-critical change that requires container recreation

In this release, we migrated the Clickhouse table engines to their replicated version. The migration was automated, and we don't expect any errors. However, if you have any issues, please check the local deployment troubleshooting section or feel free to open an issue in the Opik repository.

The structure of dataset items has changed to include new dynamic fields. Dataset items logged before version 1.0.3 will still show but would not be searchable. If you would like to migrate previous dataset items to the new format, please see the dataset item migration instructions for more information.

  • Updated datasets to support more flexible data schema - This change affects how dataset items are structured and may require updates to existing dataset insertion code. See the Dataset documentation for details.
  • The context field is now optional in the Hallucination metric - This may affect existing evaluation configurations
  • Changed dataset item insertion behavior - Duplicate items are now silently ignored instead of being ingested, which may affect data collection workflows. See the Dataset documentation for details.
  • Updated OpenAI integration to track structured output calls using beta.chat.completions.parse - This may affect existing OpenAI integration code. See the OpenAI integration documentation for details.
  • Fixed issue with update_current_span and update_current_trace that did not support updating the output field - This may affect existing trace update code. See the Tracing documentation for details.
Suggest an edit

Propose a replacement for this page. The site team reviews it before applying any changes.

Export
Documentation menu