docs(release): add MCP server note to release notes (#13853)

This commit is contained in:
Harshal Sheth 2025-06-24 14:22:43 -07:00 committed by GitHub
parent f554679be4
commit d58f41c78b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -1,40 +1,38 @@
# v0.3.12 # v0.3.12
## Release Availability Date :::info
This contains detailed release notes, but there's also an [announcement blog post](https://datahub.com/blog/datahub-cloud-v0-3-12/) that covers the highlights.
:::
#### Release Availability Date
18-Jun-2025 18-Jun-2025
## Recommended CLI/SDK #### Recommended CLI/SDK
1.1.0.2 1.1.0.2
## Recommended Remote Executor #### Recommended Remote Executor
v0.3.12-acryl (recommended) / v0.3.11.1-acryl (minimum) v0.3.12-acryl (recommended) / v0.3.11.1-acryl (minimum)
## Known Issues
- Remote executor versions older than `v0.3.11.1-acryl` will not work with this release. If you're on an older version, please reach out to your DataHub representative - there may be some workarounds.
- There are two issues with the remote executor that the DataHub team is triaging: (1) for system ingestion sources, sometimes they do not get executed as expected if their schedule is repeatedly changed and (2) in rare cases, the remote executor may stop responding to new requests. In both cases, restarting the remote executor resolves the issue.
- The "remote automations" feature does not yet work. Automations must run with the default "DataHub embedded" executor. Note that remote automations is a specific capability of the remote executor; remote ingestion and observability are not affected.
- **Databricks Metadata Sync Automation**: 1) Does not yet support syncing AI-Generated Column descriptions from DataHub to Databricks. 2) When column tags are applied _first_ in Databricks, they cannot yet be edited from DataHub. This will be addressed in an upcoming release.
- The new ingestion page redesign has a known edge case where if you have multiple sources running at the same time and you switch back and forth between the Sources tab and the Run History tab, it's possible that data appears to be cleared. In order to fix this, refresh your browser to see everything is back to normal.
- The "Ingested Assets" section of the ingestion run history modal sometimes presents incorrect counts and misformats entity type names. This issue impacts v0.3.12 as well.
## Release Changelog ## Release Changelog
---
### v0.3.12 ### v0.3.12
This release includes all changes up to and including DataHub Core v1.1.0. This release includes all changes up to and including DataHub Core v1.1.0.
- Breaking Changes - Breaking Changes
- None.
- Product - Product
- **AI-Generated Documentaton** is now in Public Beta. Turn it on by going to **Settings > AI** and enabling **Documentation AI**. - [**AI-Generated Documentaton**](../../automations/ai-docs.md) is now in Public Beta. Turn it on by going to **Settings > AI** and enabling **Documentation AI**.
- **DataHub Slack Assistant** is now in Private Beta. Reach out to your DataHub representative to get access. - [**DataHub Slack Assistant**](../slack/saas-slack-app.md#datahub-slack-bot) is now in Private Beta. Reach out to your DataHub representative to get access.
- [**Hosted MCP Server**](../../features/feature-guides/mcp.md): DataHub is now a remote MCP server.
- **Data Health Dashboard V2** is here, featuring enhanced filtering capabilities for an improved user experience. - **Data Health Dashboard V2** is here, featuring enhanced filtering capabilities for an improved user experience.
- **Smart Assertion Anomaly Feedback**: You can now mark passing assertion runs as anomalous, to remove them from future training data for Smart Assertions. You can also mark failing assertions as NOT anomalies, to include the data point in the training data for Freshness, Volume, and Column assertions. - **Smart Assertion Anomaly Feedback**: You can now mark passing assertion runs as anomalous, to remove them from future training data for Smart Assertions. You can also mark failing assertions as NOT anomalies, to include the data point in the training data for Freshness, Volume, and Column assertions.
- **Data Source Management**: This release introduces a brand new ingestion management experience! View the status of your ingestion sources with a cleaner, more refined design. We're also introducing a new **Run History** tab to view all of your ingestion runs in chronological order with the capability to filter for your desired source(s). Additionally, we are now displaying users who initiated ingestion source runs whether the action was taken through the UI or CLI. Finally, we now enable you to set up permissions to allow specific users to view only the ingestion sources they should see, including fine-grained permissions for view, edit, delete, and execute. - **Data Source Management**: This release introduces a brand new ingestion management experience! View the status of your ingestion sources with a cleaner, more refined design. We're also introducing a new **Run History** tab to view all of your ingestion runs in chronological order with the capability to filter for your desired source(s). Additionally, we are now displaying users who initiated ingestion source runs whether the action was taken through the UI or CLI. Finally, we now enable you to set up permissions to allow specific users to view only the ingestion sources they should see, including fine-grained permissions for view, edit, delete, and execute.
@ -75,3 +73,12 @@ This release includes all changes up to and including DataHub Core v1.1.0.
- Fix cursor jumping to end of text in search bar when editing a query - Fix cursor jumping to end of text in search bar when editing a query
- Retain search filters when changing your search query on the search results page - Retain search filters when changing your search query on the search results page
- Depreciation status on charts is now shown on the lineage explorer visualization - Depreciation status on charts is now shown on the lineage explorer visualization
## Known Issues
- Remote executor versions older than `v0.3.11.1-acryl` will not work with this release. If you're on an older version, please reach out to your DataHub representative - there may be some workarounds.
- There are two issues with the remote executor that the DataHub team is triaging: (1) for system ingestion sources, sometimes they do not get executed as expected if their schedule is repeatedly changed and (2) in rare cases, the remote executor may stop responding to new requests. In both cases, restarting the remote executor resolves the issue.
- The "remote automations" feature does not yet work. Automations must run with the default "DataHub embedded" executor. Note that remote automations is a specific capability of the remote executor; remote ingestion and observability are not affected.
- **Databricks Metadata Sync Automation**: 1) Does not yet support syncing AI-Generated Column descriptions from DataHub to Databricks. 2) When column tags are applied _first_ in Databricks, they cannot yet be edited from DataHub. This will be addressed in an upcoming release.
- The new ingestion page redesign has a known edge case where if you have multiple sources running at the same time and you switch back and forth between the Sources tab and the Run History tab, it's possible that data appears to be cleared. In order to fix this, refresh your browser to see everything is back to normal.
- The "Ingested Assets" section of the ingestion run history modal sometimes presents incorrect counts and misformats entity type names. This issue impacts v0.3.12 as well.