LoginSign Up
← Back to all sparks
O

OpenMetadata

ANALYTICS
Velocity5.0

Unified metadata platform for data discovery and governance

open-metadata.org ↗

A second 2.0 release candidate lands while 1.13 keeps absorbing governance and CVE fixes.

data-catalogmcpgovernanceknowledge-graphcve-patchingparallel-release-lines
◆Current state
OpenMetadata is running two lines at once. The 2.0.0 major is on its second release candidate, both explicitly marked dev and test only with no stated changes. The 1.13 line continues as the shipping product: 1.13.3 fixed Snowflake foreign-key collisions across tables sharing a constraint name, unstuck data contracts left at Running, and repaired poisoned governance trigger filters, while 1.12.14 and 1.13.2 were dominated by dependency CVE patching across MLflow, PyArrow, log4j and the ingestion images.
◆Where it's heading
The direction was set by 1.13.0, which made MCP a first-class service category and added an RDF knowledge graph; everything since has been consolidation around those two surfaces plus a heavy security-patch cadence. With 2.0 now on its second RC and carrying no published notes, the interesting question — what actually changes in the major — remains unanswered by the entries themselves.
◆Prediction
Expect further 2.0 release candidates before a final, and continued 1.13.x maintenance releases weighted toward governance-workflow fixes and dependency patching until the major stabilizes.

◆Recent moves

  1. 5d ago

    Second 2.0.0 release candidate, still dev and test only

    The second 2.0.0 release candidate, carrying the same warning as the first and no stated changes. It marks progress toward the major but publishes nothing about what the major contains.

    View source ↗
  2. 18d ago

    Snowflake foreign-key collisions and governance workflow fixes

    Snowflake foreign-key reflection is now keyed on constraint name plus table name, so cloned tables sharing a constraint no longer merge and fail ingestion. Paired with fixes for data contracts stuck at Running and governance trigger filters that rejected every event — corrective work on the governance surface 1.13.0 established.

    View source ↗
  3. 19d ago

    2.0.0 enters release candidate, dev and test only

    The first 2.0.0 release candidate opens the major's stabilization window, restricted to dev and test environments. Notable as a milestone marker rather than for any content it publishes.

    View source ↗
  4. 19d ago

    MCP tool enhancements, log4j CVE patch, reindexing fixes

    MCP tool enhancements arrive alongside a log4j CVE patch, reindexing reliability fixes and search-preview ranking corrections. The MCP refinements matter most here — they are the follow-through on the capability 1.13.0 introduced.

    View source ↗
  5. 20d ago

    MLflow, PyArrow and server dependency CVE patches

    A security-weighted release on the older 1.12 line, patching MLflow authorization and PyArrow IPC vulnerabilities plus a broad sweep of server dependencies. Test Suite reindexing and search-ranking fixes round it out.

    View source ↗
  6. 1mo ago

    MCP becomes a first-class service category with usage analytics

    ⚡ SPARK

    The release that set the direction every maintenance entry after it refines. MCP stops being an integration detail and becomes a governed asset type, and the RDF knowledge graph gives the catalog a standard query surface — the two additions that make this window more than a security-patch stream.

    View source ↗