docs/managed-datahub/release-notes/v_0_3_17.md
Patch release on top of v0.3.17.4-acryl.
27-Apr-2026
acryl-datahub dependency bumped to 1.5.0.13 to address transient assertion "source connection" errors during concurrent evaluation.Patch release on top of v0.3.17.3-acryl.
22-Apr-2026
add_documentation / remove_documentation patch helpers (documentation patch template is now available on most asset types).channel history, group history, and im history scopes are now registered as optional unless the "store conversations from Slack" feature flag is enabled, aligning with Slack's new optional scopes model so installs no longer require these scopes by default.SOURCE_CONNECTION_ERROR: 'Connection' object has no attribute 'closed' for Redshift assertions that were querying the warehouse.Patch release on top of v0.3.17.2-acryl.
17-Apr-2026
corpUserInfo.active flag for session eligibility and cleaned up related login behavior for inactive users (CUS-8505).Patch release on top of v0.3.17.1-acryl.
8-Apr-2026
Patch release on top of v0.3.17-acryl.
7-Apr-2026
GOOGLE_APPLICATION_CREDENTIALS environment variable.ion-java, and Authlib for SAC).sample_data prefix where applicable.Audit Log as the change source are now fixed.24-Mar-2026
Recommended Versions
Breaking Changes:
Deprecation We're sunsetting 'Bulk Create' on the data health dashboard, in favor of the new 'Monitoring rules' automation. This can be toggled on via observability.assertion_monitoring_rules helm flag. This requires online_smart_assertions to be enabled, and the user to have the MANAGE_TESTS privilege.
Hardcoded token signing keys have been removed for improved security. Deployments must now configure explicit signing key secrets.
Python 3.9 support has been dropped; Python 3.10+ is now required.
Security Fix The default signing key and salt values present in application.yaml used in Metadata Service Authentication have been removed. The application now requires these values to be provided via env variables DATAHUB_TOKEN_SERVICE_SIGNING_KEY and DATAHUB_TOKEN_SERVICE_SALT to the GMS deployment, consumers and other related services and jobs. IMPACT:
ACTION:
Please update your DataHub helm charts to the recommended version or above before deploying the new release.
If you are not using the DataHub helm charts to deploy, then ensure that the above variables are set in your GMS deployment and related jobs.
If the values are not set correctly you may see an error like below in your service logs.
authentication.tokenService.signingKey must be set and not be empty
or
authentication.tokenService.salt must be set and not be empty
:::note For backward compatibility you can set the value of these variables to the previous default values defined here. This is not recommended though, and it is advised to regenerate new tokens with updated keys as soon as possible. :::
Deprecations & Sunsets
The V1 UI theme is now officially sunset. All new features and patches going forward will be on the V2 UI (THEME_V2_ENABLED=true). If you are a customer of DataHub Cloud, or started using DataHub after February 2025 (or kept your clone/fork's environment variables in-sync with upstream since then), then this is already your default experience and you do not need to change anything. To ensure you are experiencing the latest features of DataHub, please ensure the following GMS environment variables are set
THEME_V2_ENABLED=true
THEME_V2_DEFAULT=true
THEME_V2_TOGGLEABLE=false
or via helm chart in your values.yaml
datahub-gms:
theme_v2:
enabled: true
default: true
Going forward, the V1 theme and associated code will be actively removed. This will help improve UI performance and simplify the codebase for contributors.
Product
null_percentage → null_countunique_percentage → unique_countempty_percentage → empty_countzero_percentage → zero_countnegative_percentage → negative_countPlatform
Ingestion
Bug Fixes