> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/overview/changelog/2026/week-of-12-oct-2026.md).

# Week of 12 Oct 2026

Decube releases from 12 Oct 2026 to 18 Oct 2026.

{% updates format="full" %}
{% update date="2026-10-13" %}

## 1.62.0: Data Quality V2

#### Feature Release: Data Quality V2

Data Quality V2 is now available. It covers the full monitor lifecycle in one place: configure a monitor, review the cases raised when it fails, and route alerts to the right team. Find it under the new Data Quality V2 entry in the navbar. For existing customers it runs alongside Data Quality Classic, so your existing monitors keep running as before. See the [Data Quality V2 documentation](https://docs.decube.io/data-quality-v2/monitors) to get started.

Data Quality V2 supports **Snowflake**, **Databricks**, **Glue**, **Redshift**, **PostgreSQL**, **MySQL** and **Microsoft Fabric** sources.

* **\[Monitors]** Create and manage monitors from the Monitors tab with a step-by-step creation wizard. Available [monitor types](https://docs.decube.io/data-quality-v2/monitor-types) are Freshness (SLA and Staleness), Volume, Field Health (numeric, string, value-set, null, unique, zero and date checks) and Custom SQL.
* **\[Monitors]** Monitors run on a recurring schedule, or on a Manual frequency that you trigger on demand.
* **\[Monitors]** The monitor listing shows each monitor's schedule, status and last result, and can be filtered by data source, schema, schedule, status, last result and custom attributes. Filters are kept in the URL, so you can share or bookmark a view. Select multiple monitors to enable, disable, delete or run them in one action.
* **\[Monitors]** The [monitor details](https://docs.decube.io/data-quality-v2/monitors/monitor-details) page shows the latest run, latest case and pass rate, along with run history, version history and the alert rules that match the monitor.
* **\[Monitors]** Editing a monitor in a way that changes what it measures now warns you and creates a new version of the monitor. Earlier runs stay with the version that produced them.
* **\[Custom SQL]** Associate a [Custom SQL](https://docs.decube.io/data-quality-v2/monitor-types/custom-sql) monitor with one or more assets, so the monitor and any cases it raises appear on those assets. Use Test Value to run your SQL and check the number of rows it returns before you create the monitor.
* **\[Custom Attributes]** Add custom attributes to monitors, such as severity, domain or team, and use them to filter listings and to route alerts. Select the new Monitors object when you define attributes in Org Settings > Custom Attributes.
* **\[Bulk Configuration]** [Create monitors in bulk with Templates](https://docs.decube.io/data-quality-v2/create-monitors-in-bulk-with-templates): save a reusable Freshness configuration, then apply it to many tables in one workflow. Use [bulk update](https://docs.decube.io/data-quality-v2/update-monitors-in-bulk) to change the schedule, threshold, data quality dimension or attributes on many existing Freshness monitors at once. Bulk configuration supports Freshness (SLA and Staleness) monitors.
* **\[Cases]** Incidents from a failing monitor are now grouped into a case for triage. The Cases tab shows open cases, unassigned cases, average time to close and new cases from the last 7 days. You can filter cases, and close, mute, unmute or assign several at once.
* **\[Cases]** The [case details](https://docs.decube.io/data-quality-v2/cases/case-details) page shows each incident with its run graph and evidence, the case's audit history, a read-only view of the monitor version that raised the case, and the delivery status of each alert sent. Lineage is shown for some monitor types.
* **\[Alerts]** [Alerts](https://docs.decube.io/data-quality-v2/alerts) replaces per-monitor notification settings with rules. Build a rule by choosing its scope (all monitors, or specific monitors), optional filters on monitor type, custom attributes or monitor name, and one or more [channels](https://docs.decube.io/data-quality-v2/alerts/alert-channels): Slack, Email, Webhook or MS Teams. Send a test alert to each channel, and enable or disable a rule at any time.

#### New Features & Enhancements

* **\[Reports]** Added the Data Quality Scorecard V2 report type, which exports a DQ score for every V2 monitor over a chosen period. Set the data quality dimension a monitor's score counts towards when you set it up. The report includes a monitor version column, with a separate row for each version of a monitor in the period. See [Data Quality Scorecard](https://docs.decube.io/reports/asset-report-data-quality-scorecard).
* **\[Asset Details]** Schema change events are now logged and shown in the Feed tab of Asset Details.
* **\[My Account/Group Management]** Updated source-based policies for Data Quality V2. The Data Quality section is now Data Quality Classic and V2, Incidents is now Cases and incidents, and Configure monitors and alerts has moved into that section. Added a Data Quality V2 module-based policy with Manage Alerts (view, edit) and Manage Templates (edit) permissions.

#### Bug Fix

* **\[Lineage]** Fixed an issue where **Snowflake** SQL lineage failed to resolve quoted schema and table names.
  {% endupdate %}

{% update date="2026-10-12" %}

## 1.61.2: Fivetran Improvements

#### Improvements

* **\[Data Source Management]** **Fivetran** now supports **Salesforce** connections for additional configuration in lineage.
* **\[Lineage]** **Fivetran** assets are now matched to their corresponding **Snowflake** assets.

#### Bug Fixes

* **\[Export/Import]** Fixed an issue where the Export tab showed an incorrect header.
* **\[Export/Import]** Fixed an issue where item titles on the Import tab were missing the word "objects".
* **\[Lineage]** Fixed an issue where Spark lineage failed to parse **ADLS** sources that use blob endpoint URIs.
* **\[Data Source Management]** Fixed an issue where **Fivetran** metadata collection could hang on a stalled API call.
  {% endupdate %}
  {% endupdates %}
