1.11.14-release

Revert "Fix #20052: Add tier field mapping with lowercase_normalizer …

1.11.13-release

Pin min collate-sqllineage version to 2.0.2 (#26250)

1.11.12-release

⚠️ Breaking Changes

OpenLineage Kinesis Support

Refactored OpenLineage connection schema to support both Kafka and Kinesis brokers

Migration Required: The OpenLineage connection configuration structure has changed from flat Kafka-specific fields to a nested brokerConfig object. Existing configurations with fields like brokersUrl, topicName, consumerGroupName, consumerOffsets, poolTimeout, sessionTimeout, securityProtocol, sslConfig, and saslConfig at the root level will be automatically migrated to the new brokerConfig.kafkaBrokerConfig structure during the database migration to version 1.11.12. No manual intervention is required for existing deployments, but any external scripts or API integrations that create/update OpenLineage connections must be updated to use the new schema structure.

Redshift IAM Authentication Support

Added support for IAM authentication for Amazon Redshift connections
Migration Required: The Redshift connection schema has changed from a flat password field to a polymorphic authType object supporting both Basic Auth and IAM Auth. Existing configurations with password at the root level will be automatically migrated to authType.password (BasicAuth structure) during the database migration to version 1.11.12. No manual intervention is required for existing deployments, but any external scripts or API integrations that create/update Redshift connections must be updated to use the new schema structure.

Improvements

• Platform: Fixed RTL layout issues and translations for Hebrew language selection

Fixes

• Platform: Resolved intermittent OAuth login failures by adding SameSite=None attribute to session cookies for cross-site authentication flows

1.11.11-release

Changelog

Breaking Changes

• Extended the REST connector to support OpenAPI schemas from local files (JSON/YAML) in addition to HTTP URLs via the openAPISchemaConnection union type.
• Updated the REST connector connection configuration to accept either connection type. Refer to this YAML example
  to review the updated connection structure.

Improvements

• Connectors: Snowflake connector now quotes identifiers in GET_DDL queries to support tables with special characters in their names.
• Connectors: Snowflake connector now skips fetching definitions of Snowflake stages as they are not relevant for metadata ingestion.
• Ingestion: Improved memory management in dbt ingestion to prevent out-of-memory errors when listing files from GCS.

Fixes

• Connectors: Fixed CSV parsing and table name errors during Datalake metadata ingestion.
• Governance: Fixed scroll functionality in Data Product pages with large descriptions.
• UI: Fixed global domain filter translation not updating when changing application language.

1.12.1-release

Features

AI Studio (Collate - Beta)

Collate already hosted AI Agents that users could control via Applications, to generate descriptions, add Tiers, and Data Quality tests. AI Studio now provides visibility and control over AI agents powering the data platform.

With AI Studio, users can customize the prompts of these agents so their output aligns with organizational needs. Moreover, admins can create new AI agents with specific behavior, capabilities and prompts, that can be executed or embedded in external AI Platforms thanks to the Metadata AI SDK.

Metadata AI SDK

The Metadata AI SDK enables programmatic access to Collate's AI agents and semantic layer, allowing teams to build custom chatbots, automate governance tasks, and integrate metadata intelligence into external applications.
By creating Agents either via the UI in AI Studio or through the Metadata AI CLI, you can now access lineage information, quality metrics and business context through simple APIs based on Natural Language.
The Metadata AI SDK is available via CLI and programmatic access in Java, Python, and Node.js.
OpenMetadata users can also leverage the AI SDK by bringing MCP tooling easily into their langchain applications, adding all the necessary semantic intelligence into their agents!

Auto Classification with Custom Recognizers (Collate)

OpenMetadata already had an Auto Classification Metadata Agent that automatically tagged PII Sensitive data. With release 1.12, Collate brings the ability to create custom AI-powered recognizers for any classification using regex patterns, column names, and data content scanning.
Moreover, users can report false positives with explanations, creating a feedback loop that improves model accuracy and ensures that the agent does not make the same mistakes again.

Data Quality Test Library

Release 1.12 takes Data Quality capabilities one step further than any other platform by letting admins create reusable, parameterized SQL-based test templates easily from the UI. Define tests once with parameters like table_name and column_name or any other custom parameter your users need, then apply consistently across multiple tables without rewriting SQL.
Users can then apply these new tests via the UI, giving them centralized governance and standardized definitions for critical business rules organization-wide.

Data Diff Column/Row Analysis (Collate)

Granula tables ar visual comparison of differences between source and target column, row, and character level. Identify which columns were added, removed, or modified with side-by-side comparison. Drill down to specific rows and see character-level changes within fields. Visual diff interface accelerates troubleshooting and root cause analysis.

GitHub Metadata Sink (Collate - Beta)

Bring metadata under version control with automated Git commits for every metadata change in Collate. If you are using separate development and production environments, routing metadata changes through GitHub pull requests brings you a human in the loop experience for any event that you might want to push into higher environments via CICD.

Human & AI Audit Logs

While every asset already supported version history, OpenMetadata now supports a comprehensive audit logs track all user and AI agent actions across the platform.
With a six-month retention, filtering by user, agent, time range, or action type as well as export capabilities, your governance teams can easily handle compliance reporting and security audits.

Column Bulk Operations

How can your teams keep up with an always growing and evolving Data Platform? Users can now aggregate identical column names across all asset types (tables, topics, containers, APIs, search indexes) in a single view to set descriptions, tags, and glossary terms for all instances simultaneously.
This aggregate view also helps users detect inconsistencies where the same column has different definitions, as well as digging into specific elements by filtering operations by domain, tags or even metadata completeness.

Column Details Panel

Added an expandable details panel for columns. Users can now view column-level custom properties and metadata directly within the table view. The panel also includes a dedicated Data Quality section for quick visibility into column health. This eliminates the need to navigate away to access column details and quality insights.

Open Standards: ODCS 3.1 & OpenLineage Support

Import and export contracts in Open Data Contract Standard (ODCS) 3.1 format for interoperability with other tools. Collate's contract specification extends ODCS with terms of service, semantic relationships, and ownership details while maintaining compatibility.
OpenMetadata also accepts events from OpenLineage, so you can now easily bring any OpenLineage-compatible systems through native API integration and benefit from the broader metadata semantics available in the platform.

AskCollate Enhancements & MS Teams Integration (Collate)

• Expanded entity support for Metrics, Knowledge Center articles, and Dashboard Data Models.
• AskCollate now holds your company’s context from glossary terms, metrics, and knowledge center. Pushing towards your governance initiatives also improves your AI tooling and interactions!
• Enhanced thinking transparency showing detailed reasoning process
• MS Teams integration alongside existing Slack integration, allowing your users to interact with AskCollate directly where they are without having to jump from tool to tool.

Kubernetes Orchestrator

OpenMetadata now brings a Kubernetes Orchestrator for those users that don’t want to use Airflow to manage the Metadata Agents and other automations. With this new orchestrator, OpenMetadata doubles-down on a simplified deployment experience, while ensuring scalability and operational efficiency in production k8s environments.

MCP Tools & Semantic Search

We have added more tooling to OpenMetadata’s MCP, helping you to create lineage, as well as adding all necessary DQ tooling around test definitions, test case creation and Root Cause Analysis.
We have also been working on the feedback shared on MCP from the community, so keep sharing your thoughts on how we can make MCP even better.
Moreover, the 1.12 release brings Semantic Search into OpenMetadata! You can enable it in the configuration to create vector embeddings for your entities, supporting both Bedrock and OpenAI embeddings. On top of that, we have created an MCP tool for Semantic Search so that you can interact with these vectors in your applications!

New Connectors

• SFTP: Catalog unstructured files alongside structured data
• Redshift Serverless: Native support for Amazon's serverless deployment option
• StarRocks: Support for open-source analytical database
• Microsoft Fabric (collate - beta): Connect to Microsoft's unified data platform including Data Warehouse, Power BI, and pipelines
• Dremio (collate): Support for lakehouse platform with query engine and semantic layer integration
• Mulesoft (collate): Integration with API management platform for API metadata and lineage

Breaking Changes

OpenSearch/Elastic Search Client have been upgraded , it is necessary to use 9.3.0 for Elasticsearch and 3.4.0 for Opensearch

Data Contract Schema Changes

Security, SLAs and Terms of Use can now be inherited from the Data Product’s Data Contract. To allow for this, we’ve added the ‘inherited’ property to Security and SLAs, and converted ‘termsOfUse’ from a simple Markdown field to an object that holds both the markdown information and the inheritance flag.

Helm

• Updated Airflow section

From here, the ‘pipelineServiceClientConfig’ key, used to host directly Airflow configuration. Now we support also a native k8s orchestration engine, so we’ve added a ‘‘pipelineServiceClientConfig’.type’ key to switch between “airflow” or “k8s”, and moved orchestrator-specific configurations into another nested level: “‘pipelineServiceClientConfig.airflow” and “‘pipelineServiceClientConfig.k8s”.

Changelog

Additional Enhancements

• Learning Resources (?): Contextual tutorials and videos throughout UI based on current page, with admin customization for organization-specific training materials
• Lineage Improvements: Column-only filtering, edge highlighting on hover, stored procedure support in edit mode, faster SQL parsing for complex lineages
• Explore Page Sidebar: Right-side navigation showing lineage, data quality details, and custom properties without leaving explore view
• Metadata Exporter - Entity History (Collate): Export complete change tracking to data warehouses for custom dashboarding, running within customer networks
• Test Case Import/Export: Bulk operations on data quality tests at table and multi-table levels
• Data Contracts at Data Product Level: Define contracts once at data product level with automatic inheritance to all assets for Semantics, Terms of Use, Security and SLAs.
• Distributed Search Indexing: Multiple application servers share indexing workload for improved scalability
• Data Product Input/Output Ports: Support port specifications with lineage visualization for data flow
• Timezone-Aware Freshness Tests: Set specific timezones on freshness tests to prevent UTC misalignment issues
• SQL Studio - Postgres & Redshift Support (Collate): Adds Postgres and Redshift to existing Snowflake, Trino, and BigQuery support
• Snowflake Dynamic Table System Metrics: Support for INSERT, UPDATE, DELETE metrics in profiler
• Column Custom Properties: Side panel drawer interface with improved navigation.

1.12.0-release (yanked)

upgrade minimatch (#26029)

1.11.10-release

Breaking Changes

Ingestion Framework Upgrade Required

Schema changes introduced in earlier minor releases require the ingestion framework to be upgraded when moving to 1.11.10.

Changes Introduced

• 1.11.5: Added queryStatementSource field to Postgres connection
• 1.11.5: Added queryParserConfig field to Dashboard service
• 1.11.9: Added statusLookbackDays field to Pipeline service

If the ingestion framework version is older and does not support these fields, you may encounter:

• ValidationError during pipeline deployment
• Airflow DAG build failures
• Configuration parsing errors

Required Action

When upgrading to 1.11.10, you must also upgrade your ingestion framework to 1.11.10. Running mismatched versions may result in schema validation failures and pipeline deployment issues.

Changelog

Improvements

• BurstIQ Connector: Added new BurstIQ database connector.
• Athena: Implemented struct profiling following established patterns.
• UI: Added support for displayName extraction from user profile during login.
• Search & Suggestions: Excluded unused fields from suggestion API calls to improve performance.

Fixes

• BigQuery: Fixed usageLocation not being added to the connection URL.
• Oracle: Fixed stored procedure line ordering with ORDER BY clause; ensured packages are ordered before package bodies.
• DB2: Fixed iSeries connection issue.
• Dagster: Added asset key prefix configuration for lineage.
• Airflow: Fixed Task Instance link not correctly filtering by DAG.
• Metabase: Fixed dataset query type detection for native queries and improved error logging.
• Ingestion Pipeline: Fixed exit handler skipping status update when pipeline is already in a terminal state.
• Workflow Management: Resolved Flowable suspension state conflict after migration.
• Schema: Fixed Delete Table Constraint when the column is not present in the patch request.
• Usage Workflow: Fixed NoneType attribute error on cost calculation.
• CSV Import: Fixed Out-of-Memory (OOM) issue during large CSV processing.
• Data Quality: Fixed boolean parameters in test case forms that could not be toggled OFF.
• UI - Tables: Fixed nested fields repetition issue in table display.

1.11.9-release

Latest Release 🎉

Latest Release
16th February 2026
You can find the GitHub release here.

Improvements

• Workflow Automation: Enabled "Updated By," "Synonyms," "Related Terms," and "Status" fields in workflow check conditions.
• Ingestion UI: Added search functionality in the ingestion runner dropdown and added fallback logic to select Collate SaaS Runner by default during service configuration.
• Unity Catalog: Optimized lineage retrieval by using system tables instead of the API.
• Pipeline API: Added bulk APIs for checking pipeline status.
• Import/Export: General improvements to import/export functionality.

Fixes

• Databricks:
  • Fixed view definition extraction.
  • Resolved circular lineage issues and extra lineage generation for self-referencing table columns.
• Ingestion & Connectors:
  • BigQuery: Fixed project ID input handling in the ingestion class.
  • Trino: Fixed shadowing of the http_scheme argument.
  • Airflow: Added DriveService to the entity class map.
  • Stability: Fixed source hash instability during ingestion runs to prevent unnecessary updates.
• CSV & Import:
  • Fixed CSV parsing logic for escape characters (handling /" -> ").
  • Resolved timeout issues during CSV imports.
  • Fixed column tag insertion and removal during Database Service imports.
• UI & User Experience:
  • Fixed issue where nested columns were not updating in real-time.
  • Added auto-scroll to form errors when they occur.
  • Fixed translation for "most-viewed-data-assets."
  • Fixed filters for Impact Analysis.
• Notifications: Fixed issue where sourceHash-only changes were generating unwanted notification emails.
• Search & Indexing: Fixed aggregation incident re-indexing.
• SDK: Added missing Data Quality parameters.

Full Changelog: 1.11.8-release...1.11.9-release

1.12.0-rc1-release

DO NOT use this in PROD

This is a Release Candidate for the upcoming 1.12.0 release and there will be changes until the final release is published.

Please, only use it in DEV/TEST environments to provide any feedback or migration issues you encounter.

1.11.8-release

Improvements

• Added BigQuery lineage support for PowerBI .pbit files
• Added sobjectNames field for multi-object selection in Salesforce connector
• Added PBI rdl report lineage
• Included API result properties descriptions from OpenAPI schemas

Fixes

• Fixed PowerBI .pbit parser fails on multiline DAX expressions
• Fixed tag search in mUI Tag Suggestion
• Fixed app stuck on refresh call for basic
• Fixed testsuite result summary
• Fixed okta renewal
• Fixed Ingest Schema & View Definition For Unity Catalog
• Fixed DB2 connection TLS certificate connection fix
• Fixed Snowflake View DDL Fallback To Preserve Exact Case Identifiers
• Skip and warn when autoclassification values are too long
• Deploy pipeline before DB update to prevent inconsistent state
• Clean OpenMetadataWorkflowConfig in IngestionPipeline