Collibra July 2026 release wave — DQ&O AI suggested rules GA; CLI lineage harvester EOL 31 July

Tag: S-2026-07-06-collibra-release-announcements Type: report (vendor product documentation / release notes) Author(s): Collibra (Product Resource Center) Date of source: 2026-07-06 (living documentation pages, fetched this date; individual items carry their own announcement-release markers) Date ingested: 2026-07-06 Authority weight: medium — primary vendor documentation, authoritative for dates and availability status but self-interested on capability descriptions; the DQ&O GA items are search-derived, not directly fetched (see raw file). Raw file: S-2026-07-06-collibra-release-announcements.md. External URL: https://productresources.collibra.com/docs/collibra/latest/Content/ReleaseNotes/ref_announcements.htm

What it claims

Collibra’s July 2026 release wave has three strands. First, in Data Quality & Observability, “AI suggested rules” and a “DQ program dashboard” reach general availability in July 2026; AI suggested rules is described as automating “creation of technical data quality rules from governance policies using GenAI” with deployment across data sources (search-derived — see authority note). Second, the 2026.07 platform release (scheduled 19 July 2026) changes integration behaviour: the Import API continueOnError default flips from false to true (favouring smaller incremental transactions over all-or-nothing imports), and a new option stops imports needlessly updating lastSyncDate on external mappings, with several /mappings API properties deprecated. Third, two End-of-Life deadlines fall on 31 July 2026: the standalone CLI lineage harvester (superseded by technical lineage via Edge) and the single-file custom technical lineage definition (superseded by batch definition).

Notable quotes

“We are now announcing the deprecation of the CLI lineage harvester, which will officially reach its End of Life on July 31, 2026.” — Collibra Announcements page (announced with release 2025.07)

“Starting with Collibra version 2026.07, the default value of the Import API continueOnError parameter changes from false to true.” — Collibra Announcements page (announced with release 2026.04)

What’s speculative vs. asserted

• Asserted (primary, fetched): the 31 July 2026 EOL dates for the CLI lineage harvester and single-file lineage definition; the 2026.07 continueOnError and lastSyncDate changes and API deprecations.
• Asserted but not directly verified: the July GA of AI suggested rules and the DQ program dashboard, and the 19 July release date — these come from search-result summaries of Collibra’s DQ release notes and release calendar, not a direct fetch.
• Speculative / vendor framing: that GenAI-suggested DQ rules reduce steward workload effectively; no independent evaluation, and no EU/UK FS reference customer named.

Topics this feeds

• BCBS 239 and Data Lineage — lineage tooling migration deadline bears on how banks maintain lineage evidence.

Open questions raised

• Whether AI-suggested DQ rules provide the explainability/auditability a regulated firm needs to rely on them as BCBS 239 data-quality controls (not addressed in the material).
• How many FS deployments still run the CLI lineage harvester and face a hard migration-to-Edge deadline (unknowable from vendor docs).
• Whether the continueOnError default change silently weakens transactional integrity assumptions in existing FS integration pipelines (flagged by Collibra as requiring review, impact firm-specific).