---
description: "DataHub Cloud v0.3.13 release notes from July 2025 with Iceberg REST Catalog improvements, domain scaling, and lineage column fixes."
---

# v0.3.13

:::info

This contains detailed release notes, but there's also an [announcement blog post](https://datahub.com/blog/datahub-cloud-v0-3-13/) that covers the highlights.

:::

#### Release Availability Date

31-Jul-2025

#### Recommended Versions

- **CLI/SDK**: 1.2.0.6
- **Remote Executor**: v0.3.13.2-acryl (recommended), v0.3.13.1-acryl, v0.3.13-acryl, v0.3.12.4-acryl, v0.3.11.1-acryl
- **On-Prem Versions**:
  - **Helm**: 1.5.80
  - **API Gateway**: 0.5.3
  - **Actions**: 0.0.13

## Release Changelog

### v0.3.13.3-acryl

This is a maintenance release including all of the changes from v0.3.13.2-acryl along with the following fixes and changes:

Bug Fixes:

- Fixes column-level lineage for charts and V2 field paths, so that it appears again
- Fixes issue with combining owners on siblings pages where an actor set multiple times with different ownership types only showed up once. Now all unique owners will properly be shown on siblings pages

### v0.3.13.2-acryl

This is a maintenance release including all of the changes from v0.3.13.1-acryl along with the following fixes and changes:

Minor improvements:

- Iceberg REST Catalog improvements
  - Show total table files size in Dataset profile for Iceberg tables
  - Show partition key field info in Dataset Schema for Iceberg tables
  - Report Iceberg tblproperties via Dataset properties
  - Better browsepaths for Iceberg tables and views.
- Update Domains management to improve scaling with many Domains in an instance to fix issues seen with loading many domains at one time.
- Prevent users from breaking our search API by requesting for assets outside of the 10k asset boundary by going to the last page with 30 results per page.
- Display the assigned roles for a given proposal in the UI to make it clearer who will see this proposal
- Adds helpful tooltips to the Icons in the Manage Data Source page
- Shows better messages while downloading large number of search results (10k+ assets)
- Shows better and actionable error messages while removing a Data product from an asset

Fixes:

- Fix issue with inability to clear descriptions on columns with sibling entities
- Fix a bug with proposed documentations where assignees were getting unnecessarily removed
- Fix issue where users with a role through a group they were in were not seeing proposals that they should see in their inbox
- Fix issue where duplicate owners can get added when adding owners through a compliance form if the owner already existed with a legacy ownership type
- Fixed issue displaying transformational leaves in the lineage visualization, when the leaf is in a cycle with the home node
- Fixed issue showing phantom connections in the lineage visualization by adding a check that upstream/downstream schema field exists
- Fixes issue with Data Quality section under a Data Contract, where Custom Assertion descriptions not being rendered properly
- Fixes UX issues with glossary terms where the option to remove it's relationship overshadows the custom links of the related term making it difficult for the user to click these links
- Fixes issue with non-required descriptions in Compliance forms where wrong strings are being saved when tried to save an empty string
- Fixes issues with Editing an Ingestion source where the users were unable to edit the 'Advanced' fields

New Features:

- Quickly tune Smart Assertion predictions with an intuitive new UI
- Bulk-create subscriptions in the Bulk-create flow on the Data Health page
- Create a group in the subscriptions UI

Known Issues:

- Going to one of the last pages of search results can result in timeouts and no results shown if the result set count is near the limit (10,000 results). This is due to a limitation with large offsets not scaling with Elasticsearch very well. We have alternative APIs for scrolling across entities, but in the search UI we use pages and offsets.
- Column-level lineage in the visualization does not appear for charts or V2 field paths

### v0.3.13.1-acryl

This is a maintenance release including all of the changes from v0.3.13 along with the following fixes and changes:

Minor improvements:

- Tweak the ingestion run status page to exclude entities that don't have a search card
- Tweak some colors for info messages on ingestion run status page
- Added ability to filter bulk-create assertions by Dataset Environment
- Tighter Smart Assertion Predictions by default
- Improved slack alert and UI formatting of assertion results
- Improved alignment of app logo with certain custom logo dimensions
- Added more fields to Access Workflow events - the urn, name, qualified name, and type of the entity being requested access if provided. Important for anyone integrating with private beta **Access Workflows** feature.
- Fixes and updates to SCIM Integration with Okta. See [SCIM Integration: Okta and DataHub](../configuring-identity-provisioning-with-okta.md)

Critical fixes:

- Anomaly feedback previously always operated on the latest run, now it operates on the actually selected run
- Metric floors and ceilings are now applied as expected
- Prevent Smart assertion SQL filters from being dropped
- Anomalous data points are automatically filtered out as expected now
- Slack installation endpoint now accepts empty dictionaries for optional parameters

### v0.3.13-acryl

This release includes all changes up to and including DataHub Core v1.2.0.

- Breaking Changes

  - All DataHub Python packages now require Python 3.9+. This affects the following packages:
    - `acryl-datahub` (DataHub CLI and SDK)
    - `acryl-datahub-actions`
    - `acryl-datahub-airflow-plugin`
    - `acryl-datahub-prefect-plugin`
    - `acryl-datahub-gx-plugin`
    - `acryl-datahub-dagster-plugin` (already required Python 3.9+)
  - #13619: The `acryl-datahub-airflow-plugin` has dropped support for Airflow versions less than 2.7.
  - #14054: The v1 plugin in `acryl-datahub-airflow-plugin` has been removed. The v2 plugin has been the default for a while already, so this should not impact most users. Users who were explicitly setting `DATAHUB_AIRFLOW_PLUGIN_USE_V1_PLUGIN=true` will need to either upgrade or pin to an older version to continue using the v1 plugin.
  - #14015: In the sql-queries source, the `default_dialect` configuration parameter has been renamed to `override_dialect`. This also affects the Python SDK methods:
    - `DataHubGraph.parse_sql_lineage(default_dialect=...)` → `DataHubGraph.parse_sql_lineage(override_dialect=...)`
    - `LineageClient.add_lineage_via_sql(default_dialect=...)` → `LineageClient.add_lineage_via_sql(override_dialect=...)`
  - #14059: The `acryl-datahub-gx-plugin` now requires pydantic v2, which means the effective minimum supported version of GX is 0.17.15 (from Sept 2023).
  - #13601: The `use_queries_v2` flag is now enabled by default for Snowflake and BigQuery ingestion. This improves the quality of lineage and quantity of queries extracted.

- Product

  - [**DataHub AI in Slack**](../slack/saas-slack-app.md#datahub-ai-in-slack): The AI-powered `@DataHub` Slack command is now available in public beta. Admins can enable this feature by navigating to UI → Settings → AI.
  - **Customizable Home Page**: Introducing a brand new home page experience with customization to suit your personal or organizational needs! Currently in private beta behind a feature flag, this new home page allows users with permission to create or edit modules for a custom default experience for all users in your organization. Alternatively, users can individually update their own personal home page to suit their needs. Configure custom asset collections, hierarchy views, documentation, pinned links and more!
  - **Entity Profile Design Updates**: Entity profile pages receive a tabs design uplift in this release with sleeker, simpler-looking tabs that bring a more consistent feel to the page.
  - **Access Workflows**: Introducing support for creating access approval workflows with custom entry points, custom form fields, routing policies, and more using the `upsertActionWorkflow` GraphQL API. Also introduced support for creating & reviewing access workflows via the **Task Center**. This is in private beta currently, available behind a feature flag (ACTION_WORKFLOWS_ENABLED).
  - **Bulk Create Field Metric Smart Assertions**: When creating a field metric assertion, you now have the ability to 'Bulk create smart assertions'. This allows you to select multiple fields and metrics, and spin up anomaly monitors across all of them in one go
  - **Bulk Create Freshness and Volume Smart Assertions**: On the data health page you can now create smart freshness and volume assertions across thousands of tables in one go. Makes it effortless to strap a seatbelt with anomaly monitors across your landscape.
  - **Improved Notifications for Assertion Failures**: Slack and email alerts for assertions failures will now include context around expected vs actual values, making it easier to separate signal from noise right where you work.
  - **Assertion Notes**: Add notes to assertions, capturing troubleshooting tips and other critical context for data producers who are responsible for maintaining the quality of the checks.
  - **Floors and Ceilings for Metric Predictions**: Smart assertions on metrics like volume and null percentage now have ceilings and floors to accurately capture the absolute limits of the metrics
  - **Preview exclusion windows in assertions timeline**: The historical assertions timeline viz now displays exclusion windows that were applied to filter out bad training data
  - **Container filters on Data Health dashboard**: Filter your data health dashboard by the asset's container, making it easy to see health of specific schemas in your database.
  - **Data Health Filters reflected in URL**: This makes it easy to bookmark and share links to specific filtered pages on the Data Health dashboard.
  - [**MCP Server**](../../features/feature-guides/mcp.md): The search tool has been revamped to improve LLM understanding and reduce tool confusion / tool call error by ~60%.
  - [**AI-Generated Documentation**](../../automations/ai-docs.md): We can now generate docs for tables with up to 3000 columns, increasing the previous limit of 1000.
  - **Upstream Propagation** The tag and glossary term propagation automations now support propagating via lineage upstream. This feature is still
    in open beta; reach out to your DataHub Cloud representative to get access.

- Ingestion

  - For Snowflake and BigQuery, query extraction v2 has been enabled by default. This feature has been validated in beta for 6+ months, and improves the quality of lineage and usage, the quantity of queries extracted, and the overall ingestion performance.

- Platform

  - #6024 - Fix Auth Validation with System User
  - #6025 - Fix Owner Types Hook Regression
  - #6092 - Fix Cast Exception On ES Reindex
  - #13819 - [feat(policies): support policy privilege constraints and ingestion aspect validators](https://github.com/datahub-project/datahub/pull/13819)
  - #13828 - [feat(openapi-31): properly update openapi spec to 3.1.0](https://github.com/datahub-project/datahub/pull/13828)
  - #13865 - [feat(): lineage registry via openapi](https://github.com/datahub-project/datahub/pull/13865)
  - #13878 - [feat(openapi): entity registry api](https://github.com/datahub-project/datahub/pull/13878)
  - #13898 - [feat(monitoring): modernize datahub monitoring](https://github.com/datahub-project/datahub/pull/13898)
  - #13942 - [feat(secret): increase secret encryption strength](https://github.com/datahub-project/datahub/pull/13942)
  - #14033 - [feat(rest_emitter): support delete emit mcp](https://github.com/datahub-project/datahub/pull/14033)
  - #14057 - [feat(search): custom search configuration for highlighting](https://github.com/datahub-project/datahub/pull/14057)
  - #14096 - [Query Graph Edge Performance Improvement](https://github.com/datahub-project/datahub/pull/14095)
  - #14156 - [feat(kafka-consumer): micrometer kafka consumer metrics](https://github.com/datahub-project/datahub/pull/14156)

- Bug Fixes
  - Search Filters - Allow searching for values on structured property filters outside of the initial set of provided values from the server. The limitation here is that your search must include the full value you are looking for in order to filter on it.
  - Freshness smart assertions have been updated to look at when operations were actually applied on the source data. Previously they used the timestamp when the operation metadata was ingested into DataHub. This is a critical fix for Freshness Smart Assertions.
  - The UI to create smart assertions for Views now defaults to Query the view for row count. Previously it looked at the warehouse's info schema by default, which always errored since info schemas don't capture metrics on Views.

## Known Issues

- If the `global.serverEnv` is not configured as `global.serverEnv=on-prem`, frontend Sentry telemetry will be enabled.
- There are several known issues with the tag and term propagation automations
  - Glossary term selector search is not working in automation editor
  - Tag propagation does not get undone when a tag is deleted
  - Glossary term propagation does not get undone when the glossary term is deleted on a table
- Internal Schema Registry - The internal schema registry does not supply a compatible schema for older MCP messages. The short term recommendation is to process all MCPs before upgrading to this release.
