Fix #2730: Add tempLineageTables field to lineage details by ulixius9 · Pull Request #26487 · open-metadata/OpenMetadata

ulixius9 · 2026-03-13T14:48:08Z

Summary

fix https://github.com/open-metadata/openmetadata-collate/issues/2730

Adds a new tempLineageTables field to LineageDetails schema as an array of {fromEntity, toEntity} objects to track lineage paths through temporary/intermediate tables
Merges converging temp table paths (e.g. source→t1→target and source→t2→target) into a single lineage request instead of overwriting, fixing a bug where parallel temp tables were lost
Maps the new field through to Elasticsearch via EsLineageData schema and LineageRepository.java so the /getLineage API returns temp table info
Adds sample data entries demonstrating both linear and converging temp table patterns
Adds 47 unit tests covering hop building, path merging, and end-to-end graph processing

Test plan

All 47 unit tests pass (pytest tests/unit/lineage/test_temp_table_lineage.py)
Verify converging temp table scenario on Snowflake: source→t1→target + source→t2→target produces merged tempLineageTables with all 4 hops
Verify /getLineage API returns tempLineageTables field after rebuild
Run mvn spotless:apply after Java build

🤖 Generated with Claude Code

github-actions · 2026-03-13T14:52:32Z

✅ TypeScript Types Auto-Updated

The generated TypeScript types have been automatically updated based on JSON schema changes in this PR.

github-actions · 2026-03-13T14:57:43Z

🛡️ TRIVY SCAN RESULT 🛡️

Target: `openmetadata-ingestion-base-slim:trivy (debian 12.13)`

Vulnerabilities (257)

Package	Vulnerability ID	Severity	Installed Version	Fixed Version
`imagemagick`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6-common`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`imagemagick-6.q16`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-arch-config`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6-headers`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-6-extra`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-6.q16-dev`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickcore-dev`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6-headers`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-6`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-6.q16-dev`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25897	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25898	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25968	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25983	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25986	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25987	🔥 CRITICAL	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-24481	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-24485	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25795	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25796	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25799	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25965	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25970	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25988	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-25989	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-26066	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-26283	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`libmagickwand-dev`	CVE-2026-27798	🚨 HIGH	8:6.9.11.60+dfsg-1.6+deb12u6	8:6.9.11.60+dfsg-1.6+deb12u7
`linux-libc-dev`	CVE-2025-37786	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2025-37822	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2025-38201	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2025-40082	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2025-71089	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2025-71238	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2026-23111	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2026-23112	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2026-23193	🚨 HIGH	6.1.162-1	6.1.164-1
`linux-libc-dev`	CVE-2026-23209	🚨 HIGH	6.1.162-1	6.1.164-1

🛡️ TRIVY SCAN RESULT 🛡️

Target: `Java`

Vulnerabilities (37)

Package	Vulnerability ID	Severity	Installed Version	Fixed Version
`com.fasterxml.jackson.core:jackson-core`	CVE-2025-52999	🚨 HIGH	2.12.7	2.15.0
`com.fasterxml.jackson.core:jackson-core`	GHSA-72hv-8253-57qq	🚨 HIGH	2.12.7	2.18.6, 2.21.1, 3.1.0
`com.fasterxml.jackson.core:jackson-core`	CVE-2025-52999	🚨 HIGH	2.13.4	2.15.0
`com.fasterxml.jackson.core:jackson-core`	GHSA-72hv-8253-57qq	🚨 HIGH	2.13.4	2.18.6, 2.21.1, 3.1.0
`com.fasterxml.jackson.core:jackson-core`	GHSA-72hv-8253-57qq	🚨 HIGH	2.15.2	2.18.6, 2.21.1, 3.1.0
`com.fasterxml.jackson.core:jackson-databind`	CVE-2022-42003	🚨 HIGH	2.12.7	2.12.7.1, 2.13.4.2
`com.fasterxml.jackson.core:jackson-databind`	CVE-2022-42004	🚨 HIGH	2.12.7	2.12.7.1, 2.13.4
`com.google.code.gson:gson`	CVE-2022-25647	🚨 HIGH	2.2.4	2.8.9
`com.google.protobuf:protobuf-java`	CVE-2021-22569	🚨 HIGH	3.3.0	3.16.1, 3.18.2, 3.19.2
`com.google.protobuf:protobuf-java`	CVE-2022-3509	🚨 HIGH	3.3.0	3.16.3, 3.19.6, 3.20.3, 3.21.7
`com.google.protobuf:protobuf-java`	CVE-2022-3510	🚨 HIGH	3.3.0	3.16.3, 3.19.6, 3.20.3, 3.21.7
`com.google.protobuf:protobuf-java`	CVE-2024-7254	🚨 HIGH	3.3.0	3.25.5, 4.27.5, 4.28.2
`com.google.protobuf:protobuf-java`	CVE-2021-22569	🚨 HIGH	3.7.1	3.16.1, 3.18.2, 3.19.2
`com.google.protobuf:protobuf-java`	CVE-2022-3509	🚨 HIGH	3.7.1	3.16.3, 3.19.6, 3.20.3, 3.21.7
`com.google.protobuf:protobuf-java`	CVE-2022-3510	🚨 HIGH	3.7.1	3.16.3, 3.19.6, 3.20.3, 3.21.7
`com.google.protobuf:protobuf-java`	CVE-2024-7254	🚨 HIGH	3.7.1	3.25.5, 4.27.5, 4.28.2
`com.nimbusds:nimbus-jose-jwt`	CVE-2023-52428	🚨 HIGH	9.8.1	9.37.2
`com.squareup.okhttp3:okhttp`	CVE-2021-0341	🚨 HIGH	3.12.12	4.9.2
`commons-beanutils:commons-beanutils`	CVE-2025-48734	🚨 HIGH	1.9.4	1.11.0
`commons-io:commons-io`	CVE-2024-47554	🚨 HIGH	2.8.0	2.14.0
`dnsjava:dnsjava`	CVE-2024-25638	🚨 HIGH	2.1.7	3.6.0
`io.airlift:aircompressor`	CVE-2025-67721	🚨 HIGH	0.27	2.0.3
`io.netty:netty-codec-http2`	CVE-2025-55163	🚨 HIGH	4.1.96.Final	4.2.4.Final, 4.1.124.Final
`io.netty:netty-codec-http2`	GHSA-xpw8-rcwv-8f8p	🚨 HIGH	4.1.96.Final	4.1.100.Final
`io.netty:netty-handler`	CVE-2025-24970	🚨 HIGH	4.1.96.Final	4.1.118.Final
`net.minidev:json-smart`	CVE-2021-31684	🚨 HIGH	1.3.2	1.3.3, 2.4.4
`net.minidev:json-smart`	CVE-2023-1370	🚨 HIGH	1.3.2	2.4.9
`org.apache.avro:avro`	CVE-2024-47561	🔥 CRITICAL	1.7.7	1.11.4
`org.apache.avro:avro`	CVE-2023-39410	🚨 HIGH	1.7.7	1.11.3
`org.apache.derby:derby`	CVE-2022-46337	🔥 CRITICAL	10.14.2.0	10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0
`org.apache.ivy:ivy`	CVE-2022-46751	🚨 HIGH	2.5.1	2.5.2
`org.apache.mesos:mesos`	CVE-2018-1330	🚨 HIGH	1.4.3	1.6.0
`org.apache.thrift:libthrift`	CVE-2019-0205	🚨 HIGH	0.12.0	0.13.0
`org.apache.thrift:libthrift`	CVE-2020-13949	🚨 HIGH	0.12.0	0.14.0
`org.apache.zookeeper:zookeeper`	CVE-2023-44981	🔥 CRITICAL	3.6.3	3.7.2, 3.8.3, 3.9.1
`org.eclipse.jetty:jetty-server`	CVE-2024-13009	🚨 HIGH	9.4.56.v20240826	9.4.57.v20241219
`org.lz4:lz4-java`	CVE-2025-12183	🚨 HIGH	1.8.0	1.8.1

🛡️ TRIVY SCAN RESULT 🛡️

Target: `Node.js`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `Python`

Vulnerabilities (9)

Package	Vulnerability ID	Severity	Installed Version	Fixed Version
`apache-airflow`	CVE-2025-68438	🚨 HIGH	3.1.5	3.1.6
`apache-airflow`	CVE-2025-68675	🚨 HIGH	3.1.5	3.1.6, 2.11.1
`cryptography`	CVE-2026-26007	🚨 HIGH	42.0.8	46.0.5
`jaraco.context`	CVE-2026-23949	🚨 HIGH	6.0.1	6.1.0
`starlette`	CVE-2025-62727	🚨 HIGH	0.48.0	0.49.1
`urllib3`	CVE-2025-66418	🚨 HIGH	1.26.20	2.6.0
`urllib3`	CVE-2025-66471	🚨 HIGH	1.26.20	2.6.0
`urllib3`	CVE-2026-21441	🚨 HIGH	1.26.20	2.6.3
`wheel`	CVE-2026-24049	🚨 HIGH	0.45.1	0.46.2

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/etc/ssl/private/ssl-cert-snakeoil.key`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/ingestion/pipelines/extended_sample_data.yaml`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/ingestion/pipelines/lineage.yaml`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/ingestion/pipelines/sample_data.json`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/ingestion/pipelines/sample_data.yaml`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/ingestion/pipelines/sample_data_aut.yaml`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/ingestion/pipelines/sample_usage.json`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/ingestion/pipelines/sample_usage.yaml`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/ingestion/pipelines/sample_usage_aut.yaml`

No Vulnerabilities Found

github-actions · 2026-03-13T14:58:10Z

🛡️ TRIVY SCAN RESULT 🛡️

Target: `openmetadata-ingestion:trivy (debian 12.12)`

Vulnerabilities (4)

Package	Vulnerability ID	Severity	Installed Version	Fixed Version
`libpam-modules`	CVE-2025-6020	🚨 HIGH	1.5.2-6+deb12u1	1.5.2-6+deb12u2
`libpam-modules-bin`	CVE-2025-6020	🚨 HIGH	1.5.2-6+deb12u1	1.5.2-6+deb12u2
`libpam-runtime`	CVE-2025-6020	🚨 HIGH	1.5.2-6+deb12u1	1.5.2-6+deb12u2
`libpam0g`	CVE-2025-6020	🚨 HIGH	1.5.2-6+deb12u1	1.5.2-6+deb12u2

🛡️ TRIVY SCAN RESULT 🛡️

Target: `Java`

Vulnerabilities (38)

Package	Vulnerability ID	Severity	Installed Version	Fixed Version
`com.fasterxml.jackson.core:jackson-core`	CVE-2025-52999	🚨 HIGH	2.12.7	2.15.0
`com.fasterxml.jackson.core:jackson-core`	GHSA-72hv-8253-57qq	🚨 HIGH	2.12.7	2.18.6, 2.21.1, 3.1.0
`com.fasterxml.jackson.core:jackson-core`	CVE-2025-52999	🚨 HIGH	2.13.4	2.15.0
`com.fasterxml.jackson.core:jackson-core`	GHSA-72hv-8253-57qq	🚨 HIGH	2.13.4	2.18.6, 2.21.1, 3.1.0
`com.fasterxml.jackson.core:jackson-core`	GHSA-72hv-8253-57qq	🚨 HIGH	2.15.2	2.18.6, 2.21.1, 3.1.0
`com.fasterxml.jackson.core:jackson-core`	GHSA-72hv-8253-57qq	🚨 HIGH	2.16.1	2.18.6, 2.21.1, 3.1.0
`com.fasterxml.jackson.core:jackson-databind`	CVE-2022-42003	🚨 HIGH	2.12.7	2.12.7.1, 2.13.4.2
`com.fasterxml.jackson.core:jackson-databind`	CVE-2022-42004	🚨 HIGH	2.12.7	2.12.7.1, 2.13.4
`com.google.code.gson:gson`	CVE-2022-25647	🚨 HIGH	2.2.4	2.8.9
`com.google.protobuf:protobuf-java`	CVE-2021-22569	🚨 HIGH	3.3.0	3.16.1, 3.18.2, 3.19.2
`com.google.protobuf:protobuf-java`	CVE-2022-3509	🚨 HIGH	3.3.0	3.16.3, 3.19.6, 3.20.3, 3.21.7
`com.google.protobuf:protobuf-java`	CVE-2022-3510	🚨 HIGH	3.3.0	3.16.3, 3.19.6, 3.20.3, 3.21.7
`com.google.protobuf:protobuf-java`	CVE-2024-7254	🚨 HIGH	3.3.0	3.25.5, 4.27.5, 4.28.2
`com.google.protobuf:protobuf-java`	CVE-2021-22569	🚨 HIGH	3.7.1	3.16.1, 3.18.2, 3.19.2
`com.google.protobuf:protobuf-java`	CVE-2022-3509	🚨 HIGH	3.7.1	3.16.3, 3.19.6, 3.20.3, 3.21.7
`com.google.protobuf:protobuf-java`	CVE-2022-3510	🚨 HIGH	3.7.1	3.16.3, 3.19.6, 3.20.3, 3.21.7
`com.google.protobuf:protobuf-java`	CVE-2024-7254	🚨 HIGH	3.7.1	3.25.5, 4.27.5, 4.28.2
`com.nimbusds:nimbus-jose-jwt`	CVE-2023-52428	🚨 HIGH	9.8.1	9.37.2
`com.squareup.okhttp3:okhttp`	CVE-2021-0341	🚨 HIGH	3.12.12	4.9.2
`commons-beanutils:commons-beanutils`	CVE-2025-48734	🚨 HIGH	1.9.4	1.11.0
`commons-io:commons-io`	CVE-2024-47554	🚨 HIGH	2.8.0	2.14.0
`dnsjava:dnsjava`	CVE-2024-25638	🚨 HIGH	2.1.7	3.6.0
`io.airlift:aircompressor`	CVE-2025-67721	🚨 HIGH	0.27	2.0.3
`io.netty:netty-codec-http2`	CVE-2025-55163	🚨 HIGH	4.1.96.Final	4.2.4.Final, 4.1.124.Final
`io.netty:netty-codec-http2`	GHSA-xpw8-rcwv-8f8p	🚨 HIGH	4.1.96.Final	4.1.100.Final
`io.netty:netty-handler`	CVE-2025-24970	🚨 HIGH	4.1.96.Final	4.1.118.Final
`net.minidev:json-smart`	CVE-2021-31684	🚨 HIGH	1.3.2	1.3.3, 2.4.4
`net.minidev:json-smart`	CVE-2023-1370	🚨 HIGH	1.3.2	2.4.9
`org.apache.avro:avro`	CVE-2024-47561	🔥 CRITICAL	1.7.7	1.11.4
`org.apache.avro:avro`	CVE-2023-39410	🚨 HIGH	1.7.7	1.11.3
`org.apache.derby:derby`	CVE-2022-46337	🔥 CRITICAL	10.14.2.0	10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0
`org.apache.ivy:ivy`	CVE-2022-46751	🚨 HIGH	2.5.1	2.5.2
`org.apache.mesos:mesos`	CVE-2018-1330	🚨 HIGH	1.4.3	1.6.0
`org.apache.thrift:libthrift`	CVE-2019-0205	🚨 HIGH	0.12.0	0.13.0
`org.apache.thrift:libthrift`	CVE-2020-13949	🚨 HIGH	0.12.0	0.14.0
`org.apache.zookeeper:zookeeper`	CVE-2023-44981	🔥 CRITICAL	3.6.3	3.7.2, 3.8.3, 3.9.1
`org.eclipse.jetty:jetty-server`	CVE-2024-13009	🚨 HIGH	9.4.56.v20240826	9.4.57.v20241219
`org.lz4:lz4-java`	CVE-2025-12183	🚨 HIGH	1.8.0	1.8.1

🛡️ TRIVY SCAN RESULT 🛡️

Target: `Node.js`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `Python`

Vulnerabilities (25)

Package	Vulnerability ID	Severity	Installed Version	Fixed Version
`Authlib`	CVE-2026-28802	🚨 HIGH	1.6.6	1.6.7
`PyJWT`	CVE-2026-32597	🚨 HIGH	2.10.1	2.12.0
`Werkzeug`	CVE-2024-34069	🚨 HIGH	2.2.3	3.0.3
`aiohttp`	CVE-2025-69223	🚨 HIGH	3.12.12	3.13.3
`aiohttp`	CVE-2025-69223	🚨 HIGH	3.13.2	3.13.3
`apache-airflow`	CVE-2025-68438	🚨 HIGH	3.1.5	3.1.6
`apache-airflow`	CVE-2025-68675	🚨 HIGH	3.1.5	3.1.6, 2.11.1
`apache-airflow-providers-http`	CVE-2025-69219	🚨 HIGH	5.6.0	6.0.0
`azure-core`	CVE-2026-21226	🚨 HIGH	1.37.0	1.38.0
`cryptography`	CVE-2026-26007	🚨 HIGH	42.0.8	46.0.5
`google-cloud-aiplatform`	CVE-2026-2472	🚨 HIGH	1.130.0	1.131.0
`google-cloud-aiplatform`	CVE-2026-2473	🚨 HIGH	1.130.0	1.133.0
`jaraco.context`	CVE-2026-23949	🚨 HIGH	5.3.0	6.1.0
`jaraco.context`	CVE-2026-23949	🚨 HIGH	6.0.1	6.1.0
`protobuf`	CVE-2026-0994	🚨 HIGH	4.25.8	6.33.5, 5.29.6
`pyasn1`	CVE-2026-23490	🚨 HIGH	0.6.1	0.6.2
`python-multipart`	CVE-2026-24486	🚨 HIGH	0.0.20	0.0.22
`ray`	CVE-2025-62593	🔥 CRITICAL	2.47.1	2.52.0
`starlette`	CVE-2025-62727	🚨 HIGH	0.48.0	0.49.1
`tornado`	CVE-2026-31958	🚨 HIGH	6.5.3	6.5.5
`urllib3`	CVE-2025-66418	🚨 HIGH	1.26.20	2.6.0
`urllib3`	CVE-2025-66471	🚨 HIGH	1.26.20	2.6.0
`urllib3`	CVE-2026-21441	🚨 HIGH	1.26.20	2.6.3
`wheel`	CVE-2026-24049	🚨 HIGH	0.45.1	0.46.2
`wheel`	CVE-2026-24049	🚨 HIGH	0.45.1	0.46.2

🛡️ TRIVY SCAN RESULT 🛡️

Target: `usr/bin/docker`

Vulnerabilities (3)

Package	Vulnerability ID	Severity	Installed Version	Fixed Version
`stdlib`	CVE-2025-68121	🔥 CRITICAL	v1.25.5	1.24.13, 1.25.7, 1.26.0-rc.3
`stdlib`	CVE-2025-61726	🚨 HIGH	v1.25.5	1.24.12, 1.25.6
`stdlib`	CVE-2025-61728	🚨 HIGH	v1.25.5	1.24.12, 1.25.6

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/etc/ssl/private/ssl-cert-snakeoil.key`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `/home/airflow/openmetadata-airflow-apis/openmetadata_managed_apis.egg-info/PKG-INFO`

No Vulnerabilities Found

github-actions · 2026-03-13T17:22:25Z

🔴 Playwright Results — 2 failure(s), 24 flaky

✅ 3318 passed · ❌ 2 failed · 🟡 24 flaky · ⏭️ 183 skipped

Shard	Passed	Failed	Flaky	Skipped
🟡 Shard 1	452	0	3	2
🔴 Shard 2	301	2	2	1
🟡 Shard 3	650	0	8	33
🟡 Shard 4	726	0	4	47
✅ Shard 5	591	0	0	67
🟡 Shard 6	598	0	7	33

Genuine Failures (failed on all attempts)

❌ Features/Container.spec.ts › expand / collapse should not appear after updating nested fields for container (shard 2)

�[31mTest timeout of 180000ms exceeded.�[39m

❌ Features/DataQuality/TestCaseImportExportBasic.spec.ts › should upload and validate CSV file (shard 2)

Error: �[2mexpect(�[22m�[31mlocator�[39m�[2m).�[22mtoHaveText�[2m(�[22m�[32mexpected�[39m�[2m)�[22m failed

Locator:  getByTestId('passed-row')
Expected: �[32m"4"�[39m
Received: �[31m"1"�[39m
Timeout:  15000ms

Call log:
�[2m  - Expect "toHaveText" with timeout 15000ms�[22m
�[2m  - waiting for getByTestId('passed-row')�[22m
�[2m    19 × locator resolved to <span data-testid="passed-row" class="font-semibold passed-row">1</span>�[22m
�[2m       - unexpected value "1"�[22m

🟡 24 flaky test(s) (passed on retry)

Flow/Metric.spec.ts › Verify Related Metrics Update (shard 1, 1 retry)
Flow/Tour.spec.ts › Tour should work from help section (shard 1, 2 retries)
Flow/Tour.spec.ts › Tour should work from URL directly (shard 1, 1 retry)
Features/ColumnBulkOperations.spec.ts › should filter by metadata status and verify API param (shard 2, 1 retry)
Features/RTL.spec.ts › Verify Following widget functionality (shard 2, 1 retry)
Features/BulkImport.spec.ts › Database (shard 3, 1 retry)
Features/DataQuality/TestCaseImportExportE2eFlow.spec.ts › Admin: Complete export-import-validate flow (shard 3, 1 retry)
Features/DataQuality/TestCaseIncidentPermissions.spec.ts › User with TEST_CASE.EDIT_ALL can see edit icon on incidents (shard 3, 1 retry)
Features/DataQuality/TestCaseResultPermissions.spec.ts › User with TEST_CASE.EDIT_ALL can see edit action on test case (shard 3, 1 retry)
Features/LandingPageWidgets/DomainDataProductsWidgets.spec.ts › Domain asset count should update when assets are added (shard 3, 2 retries)
Features/LandingPageWidgets/DomainDataProductsWidgets.spec.ts › Data Product asset count should update when assets are removed (shard 3, 2 retries)
Features/Permissions/GlossaryPermissions.spec.ts › Team-based permissions work correctly (shard 3, 1 retry)
Features/Permissions/ServiceEntityPermissions.spec.ts › Api Service allow common operations permissions (shard 3, 1 retry)
Features/UserProfileOnlineStatus.spec.ts › Should update online status in real-time when user becomes active (shard 4, 1 retry)
Pages/Customproperties-part2.spec.ts › entityReferenceList shows item count, scrollable list, no expand toggle (shard 4, 1 retry)
Pages/Domains.spec.ts › Verify Domain entity API calls do not include invalid domains field in tag assets (shard 4, 1 retry)
Pages/Entity.spec.ts › Glossary Term Add, Update and Remove (shard 4, 1 retry)
Pages/Glossary.spec.ts › Change glossary term hierarchy using menu options across glossary (shard 6, 1 retry)
Pages/Glossary.spec.ts › Column dropdown drag-and-drop functionality for Glossary Terms table (shard 6, 1 retry)
Pages/InputOutputPorts.spec.ts › Cancel adding port (shard 6, 1 retry)
Pages/Lineage.spec.ts › Lineage creation from ApiEndpoint entity (shard 6, 1 retry)
Pages/ODCSImportExport.spec.ts › Multi-object ODCS contract - object selector shows all schema objects (shard 6, 1 retry)
Pages/ServiceEntity.spec.ts › Tier Add, Update and Remove (shard 6, 1 retry)
Pages/Users.spec.ts › Permissions for table details page for Data Consumer (shard 6, 1 retry)

📦 Download artifacts

How to debug locally

# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip    # view trace

github-actions · 2026-03-14T01:54:35Z

✅ TypeScript Types Auto-Updated

The generated TypeScript types have been automatically updated based on JSON schema changes in this PR.

github-actions · 2026-03-14T02:15:51Z

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	66.04% (57439/86967)	45.65% (30397/66579)	48.63% (9107/18726)

gitar-bot · 2026-03-16T09:23:12Z

Code Review ✅ Approved 1 resolved / 1 findings

Adds tempLineageTables field to lineage details, fixing the table_chain reset issue that was causing incorrect hop counts between entity pairs.

✅ 1 resolved

✅ Bug: table_chain never resets between entity pairs → wrong hops

📄 ingestion/src/metadata/ingestion/lineage/sql_lineage.py:1216 📄 ingestion/src/metadata/ingestion/lineage/sql_lineage.py:1134 📄 ingestion/src/metadata/ingestion/lineage/sql_lineage.py:1062
In both _collect_temp_lineage_hops and _process_sequence, table_chain is initialised once before the for node in sequence loop and only ever appended to. When a path contains more than two resolved entities (e.g. realA → tmp1 → realB → tmp2 → realC), the chain for the second pair (realB → realC) is [realA, tmp1, realB, tmp2, realC] instead of the expected [realB, tmp2, realC].

_build_temp_table_lineage then produces spurious intermediate hops (e.g. realB_fqn → tmp1, tmp1 → realB) because it walks the full chain using positional indices.

The old code only used table_chain for a debug-style masked_query string, so the stale entries were cosmetic. Now that the chain drives structured TempLineageTable objects that are surfaced through the API and indexed in Elasticsearch, the bug produces materially incorrect lineage data.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

`Auto-apply`	`Compact`
`gitar auto-apply:on`	`gitar display:verbose`

_{Was this helpful? React with 👍 / 👎 | Gitar}

sonarqubecloud · 2026-03-16T09:50:57Z

Quality Gate passed for 'open-metadata-ui'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

sonarqubecloud · 2026-03-16T10:21:12Z

Quality Gate passed for 'open-metadata-ingestion'

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

open-metadata#26487) * Fix open-metadata#2730: Lineage Add Temp Node Support * missing sql file * Update generated TypeScript types * Update generated TypeScript types * address guitar commens --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

* * fixed kafka sink linage * fix kafka pipline linage topic to table matching * chore(ui): add sidebar navigation (#26498) * chore(ui): add sidebar navigation * fix * Migrated CustomControls and BulkImportVersionSummary (#26410) * Migrated CustomControls and BulkImportVersionSummary * migrated styled button component and playwright fixes * fixed unit test * fixed the bulkimportsummary modal and custom control tab item * fixed the sonar issue * addressed pr comments * fixed playwright * fixed playwright and lint issues * addressed gitar comment --------- Co-authored-by: Shailesh Parmar <shailesh.parmar.webdev@gmail.com> * refactor: update toggle component and related fields to use UT_SWITCH type (#26425) * refactor: update toggle component and related fields to use UT_SWITCH type * addressed gitar comment * fixed unit tests * addressed PR comment * Chore(deps): Bump undici in /openmetadata-ui/src/main/resources/ui (#26497) Bumps [undici](https://github.com/nodejs/undici) from 6.23.0 to 6.24.1. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v6.23.0...v6.24.1) --- updated-dependencies: - dependency-name: undici dependency-version: 6.24.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(ui): fix UserTeamSelectableList closing when clicking inside popover in modal (#26502) * Remove unused `/api/v1/domains?limit=10000&fields=parent` call on every page load (#26485) * Initial plan * Remove unused domain list API call on every page load Co-authored-by: karanh37 <33024356+karanh37@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: karanh37 <33024356+karanh37@users.noreply.github.com> * feat: migrate DeleteModal from MUI to untitledUI components (#26461) * feat: migrate DeleteModal from MUI to untitledUI components * fixed the import * comment addressed * fix: remove unnecessary span element from DeleteModal * refactor: remove DeleteModal component and its associated files * addressed gitar comment * Added unit tests * MINOR: Informix Schema update (#26483) * MINOR: Informix Schema update * fix * Update generated TypeScript types * Add supportdatabase * Update generated TypeScript types --------- Co-authored-by: Akash Verma <akashverma@Akashs-MacBook-Pro-2.local> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Mayur Singal <39544459+ulixius9@users.noreply.github.com> Co-authored-by: Anujkumar Yadav <anujf0510@gmail.com> * ui: make search placeholder in service main tabs dynamic (#26511) * Revert "feat: migrate DeleteModal from MUI to untitledUI components (#26461)" (#26519) This reverts commit 8327d22. * Revert "refactor: update toggle component and related fields to use UT_SWITCH…" (#26520) This reverts commit 59fe777. * fix(ui): Test suite add-test-case modal and table UX (#26512) * fix(ui): Test suite add-test-case modal and table UX * fix footer padding * Add eslint-plugin-playwright enforcement with CI check (#26494) * Add eslint-plugin-playwright enforcement with CI check Add eslint-plugin-playwright to catch common Playwright anti-patterns automatically. 13 rules configured in two tiers: - Error (blocks CI): no-networkidle, no-page-pause, no-focused-test - Warn (tracks debt): missing-playwright-await, no-wait-for-timeout, no-force-option, no-element-handle, no-eval, no-skipped-test, prefer-web-first-assertions, no-useless-await, no-wait-for-selector, valid-expect Changes: - Install eslint-plugin-playwright, configure rules in eslint.config.mjs - Add yarn lint:playwright script - Repurpose ui-checkstyle.yml workflow to run Playwright lint on PRs - Fix last networkidle usage in ClassificationConditionalRendering - Remove stale eslint-disable comments for undefined rules - Update PLAYWRIGHT_DEVELOPER_HANDBOOK with ESLint Enforcement section - Update playwright, writing-playwright-tests, and playwright-validation skills to reference lint check Current: 0 errors, 1657 warnings (CI passes cleanly) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix CodeQL cache poisoning alert: use pull_request instead of pull_request_target Switch from pull_request_target to pull_request since this workflow only runs yarn lint:playwright — no secrets or write permissions needed. This eliminates the untrusted code execution risk flagged by CodeQL. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix all 1657 Playwright ESLint warnings across 190 files Resolve every playwright lint rule violation to enforce test quality: - no-wait-for-selector (1290): replace page.waitForSelector() with locator.waitFor() - no-wait-for-timeout (130): replace hardcoded waits with event-driven alternatives - prefer-web-first-assertions (61): use toHaveText/toBeVisible/toHaveValue - no-force-option (51): remove { force: true } bypassing actionability checks - missing-playwright-await (40): add await to fire-and-forget assertions - no-skipped-test (28): acknowledge skipped tests with eslint-disable reasons - no-eval (11): replace page.$eval with locator APIs - no-element-handle (10): replace page.$() with page.locator() - no-useless-await (8): remove await from synchronous operations - valid-expect (4): add matchers to bare expect() calls - no-networkidle (2): replace networkidle with domcontentloaded Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove unnecessary ANTLR install and add --frozen-lockfile to CI - Remove Install Antlr4 CLI step from playwright-lint job (not needed for ESLint, saves 10-30s and avoids external network dependency) - Add --frozen-lockfile to yarn install for reproducible CI builds Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Restore ANTLR CLI install — required by yarn postinstall script yarn install triggers build-check → js-antlr which needs antlr4 CLI. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix trivially-true assertion in special character search test Remove `(await tableRows.count()) >= 0` which is always true since count() never returns negative. The assertion now properly validates that either the table or empty state is visible after searching. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix strict mode violations: add .first() to multi-element waitFor calls The no-wait-for-selector conversion (waitForSelector → locator.waitFor) introduced strict mode violations. Playwright's Locator API throws when waitFor() matches multiple elements, unlike the old waitForSelector API. Key patterns fixed: - getByTestId('loader').waitFor() — multiple loaders on page - getByTestId('select-owner-tabs').getByTestId('loader') — tab loaders - locator('.ant-skeleton-active/content').waitFor() — multiple skeletons - locator('table/thead th').waitFor() — multiple tables - getByTestId('side-panel-classification') — multiple panels - locator('.ant-select-dropdown:visible') — multiple dropdowns - locator('.ant-popover').waitFor() — multiple popovers Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix strict mode violation in incidentManager assignee/owner-link The getByTestId('assignee').getByTestId('owner-link') locator resolves to 15 elements in the incident manager table (one per row). Adding .first() matches the original waitForSelector semantics. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix test failures from lint conversions: proper waits and retry logic - GlossaryPermissions: add waitForAllLoadersToDisappear after page nav - GlossaryP3Tests: restore waits for special char search + error state - GlossaryStatusFilterLargeDataset: restore waitForTimeout for filter state settling (no reliable DOM element to wait for) - AutoPilot: use waitForAllLoadersToDisappear instead of .first() to ensure ALL loaders are gone, increase banner timeout to 60s - importUtils: use expect().toHaveCount(0) for scoped multi-element loader/skeleton waits instead of waitForSelector or .first() - ColumnBulkOperations: increase response timeout, add retry polling for empty state verification - DomainDataProductsWidgets: add poll-based wait for DOM update after asset removal instead of removed waitForTimeout - customizeLandingPage: scope widget click to dialog to avoid matching stale elements on the page behind the modal Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Restore force:true where genuinely needed with eslint-disable comments The no-force-option ESLint rule removal broke tests where force was required for Ant Select comboboxes (selected item overlay covers input), popover triggers (partially obstructed by animation), data grid buttons (covered by overlay), and drag-and-drop (row hover overlays). Each restoration includes an eslint-disable-line comment explaining why force is necessary. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Stabilize 4 flaky tests with retry wrappers and proper waits - DataContractsSemanticRules: Wrap reload + status assertions in expect().toPass() to handle async backend contract validation - DataContracts: Increase timeout on dynamically rendered row filter and column text assertions that contain UUID-suffixed names - Customproperties-part2: Wrap user search-and-select loop in expect().toPass() retry to handle search dropdown rendering races - UserProfileOnlineStatus: Add profile render wait, navigation completion guard, and increased badge visibility timeout Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Replace .first().waitFor loader pattern with waitForAllLoadersToDisappear The pattern `page.getByTestId('loader').first().waitFor({ state: 'detached' })` only waits for the FIRST loader element to detach. When multiple loaders exist (nested components, tabs, popovers), this causes tests to proceed before the page is fully loaded — the root cause of ~18 flaky tests. Replaced ~500 occurrences across 103 files with the correct `waitForAllLoadersToDisappear(page)` which uses `expect(loaders).toHaveCount(0)` to wait for ALL loaders to disappear. Scoped loader waits (e.g., within select-owner-tabs, test-case-container, tags-container) are intentionally preserved since they correctly target a specific container's single loader. Also fixes UserProfileOnlineStatus.spec.ts: - Added createOrFetchUser helper for idempotent user creation on retries - Added afterAll cleanup for test users - Replaced waitForURL with redirectToHomePage for navigation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Karan Hotchandani <33024356+karanh37@users.noreply.github.com> * [Fix-25563] - Issue in Search Entity By Key (#26482) * Fix Issue Entity Not found , entity missing from search * Fix Tests * Fix Broken relationship issue for upstreamEntityRelationship * Add Exponential Retry * Remove Entity Not found from query * Address Reciew Comments * Address more review * Fix Missing Columns Index * Fix Join add stats * Column stats and Merged Main * Add separate custom bulk processor for column * Fix reindex job falsely killed after 1 hour by orphan monitor The OrphanJobMonitor uses job.updatedAt as a liveness signal, but updatedAt was only set during state transitions (READY, RUNNING), never refreshed during processing. After 10 minutes the job appeared orphaned; at the 1-hour recovery window it was force-failed. Fix: touch updatedAt alongside the lock refresh (every 60s) so the staleness check stays satisfied while the coordinator is alive. * Set Failure callback for columnBulkProcessor * fix review comments * address review comments from claude * Review Mocked tests * Address review comments. Both fixed: 1. retryOnConflict(3) restored on all 4 call sites — updateEntity and upsertDocument in both ElasticSearchEntityManager and OpenSearchEntityManager. This handles shard-level version conflicts independently from the 429 retry logic in SearchRetryUtil. 2. drainPendingColumnFutures race fixed in both bulk sinks — replaced iterate + clear() with poll() loop, which atomically removes each element from the deque so no concurrently-added futures can be lost * Get proper error message from Elastic and OpenSearch * Fix Breaking Test * MINOR: Port py-tests improvements to py-tests-postgres workflow (#26517) Apply the same structural improvements from the py-tests workflow: - Add integration test sharding (shard-1/shard-2) for parallelism - Replace `make run_python_tests` with nox integration-tests session - Add explicit timeout-minutes (180) and descriptive job name - Remove unnecessary fetch-depth: 0 from checkout - Normalize indentation to 2-space with proper YAML style * Use context to enhance recognition by default (#25856) * Implement custom context enhancement for Presidio recognizers Presidio's default context enhancement relies heavily on NLP and often fails when analyzing individual values rather than full text. This implements a custom context enhancement that: - Boosts recognizer scores to MAX when context keywords match - Applies a minimum score threshold (0.3) before enhancement - Skips already-enhanced results to prevent double-boosting - Introduces a decorator pattern for composing recognizer enhancements - Adds eager_us_bank_recognizer with higher base scores for better results The enhancement works by checking if any context words from the recognizer match the provided context list, then boosting the confidence score to maximum and setting the IS_SCORE_ENHANCED_BY_CONTEXT_KEY metadata flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Integrate context enhancement into recognizer factory Updates PresidioRecognizerFactory to apply the new decorator pattern: - All recognizers now use enhance_using_context decorator - Confidence threshold filtering applied via filter_enhanced_results_below_threshold - Decorators composed using decorate_recognizer for clean application - Context passed to PatternRecognizer during creation This ensures all enabled recognizers benefit from custom context enhancement while maintaining backward compatibility with confidence thresholds. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Add migration to update PII tag recognizers with enhanced configs Adds a v1.1.22 migration that updates existing PII tags with improved recognizer configurations featuring context keywords and optimized patterns. Changes: - Add patchRecognizers method in CollectionDAO for updating tag recognizers - Implement setRecognizersForSensitiveTags in MigrationUtil to load and apply recognizer configs from piiTagsWithRecognizers.json - Update piiTagsWithRecognizers.json with context keywords for better classification accuracy - Execute migration as post-DDL script for both MySQL and PostgreSQL This migration ensures existing deployments benefit from the improved context enhancement logic without manual reconfiguration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Fix potential NPE and type mismatch in migration utility Addresses code review feedback: 1. Fix potential NullPointerException in setRecognizersForSensitiveTags - Use Boolean.TRUE.equals() instead of auto-unboxing for nullable Boolean - Prevents NPE when autoClassificationEnabled is absent from JSON - Follows existing pattern from v1120/MigrationUtil.java 2. Fix Boolean vs boolean type mismatch in updateTagRecognizers - Change isForceMigration parameter from boxed Boolean to primitive boolean - Matches caller signature and eliminates latent NPE risk - Maintains consistency across method signatures 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Add context to NHSRecognizer * Fix typing * Fix broken unit tests * Fix broken integration test --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Pere Miquel Brull <peremiquelbrull@gmail.com> * Chore(UI): Remove tags customization option (#26514) * Add regenerate-bot-tokens operation for JWT key rotation (#26477) * Add regenerate-bot-tokens operation for JWT key rotation Add a new `regenerate-bot-tokens` subcommand to OpenMetadataOperations that regenerates JWT tokens for all bot users. This is needed when rotating JWT signing keys or changing the cluster name (e.g., during disaster recovery from POV to PROD). The command: - Iterates through all non-deleted bots with pagination - Regenerates JWT tokens only for bots using JWT authentication - Skips bots without associated users or non-JWT auth mechanisms - Displays results in an ASCII table with status per bot Closes open-metadata/openmetadata-collate#3157 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix review: add --expiry CLI parameter and null-guard paging - Token expiry is now a CLI parameter (--expiry) defaulting to Unlimited, so operators can choose OneHour, One, Seven, Thirty, Sixty, Ninety, or Unlimited when regenerating - Add null guard on getPaging() to prevent NPE on empty result sets Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Document regenerate-bot-tokens expiry values in help output Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Move bot token regeneration logic to server API Move the token regeneration logic from the ops CLI into a new REST endpoint PUT /v1/users/regenerateBotTokens (admin-only). The ops command now calls the server API via HTTP, following the same pattern as deploy-pipelines. This keeps business logic in the server and the ops CLI as a thin HTTP client. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Revert server API approach, use direct DB access for token regeneration After JWT key rotation, all existing bot tokens are invalid — including the ingestion-bot token needed to authenticate against the server API. This command must operate directly on the database to recover from that state. Added a doc comment explaining the reasoning. Also reverts the UserResource endpoint added in the previous commit. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix compilation: use fully-qualified ResultList to match existing pattern Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix botUser always null: fetch each bot individually via getByName listAll/listAfter use setFieldsInBulk which only calls registered fieldFetchers (tags, owners, etc.) — not the entity-specific setFields override. BotRepository.setFields populates botUser via a relationship lookup, but this is never called in bulk listing. Fetch each bot individually with getByName which triggers setFields properly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add integration tests for regenerate-bot-tokens operation Tests cover token regeneration producing new tokens, respecting expiry parameters, and handling multiple bots independently. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix flaky test: use different expiries to guarantee distinct tokens Unlimited tokens generated in the same second produce identical JWTs (same iat, null exp). Changed test to use different expiry values so the tokens are guaranteed to differ. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * format --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> * Fix #2730: Add tempLineageTables field to lineage details (#26487) * Fix #2730: Lineage Add Temp Node Support * missing sql file * Update generated TypeScript types * Update generated TypeScript types * address guitar commens --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> * Feature: Fabric's lineage, usage and profiler support (#26373) * Feature: Fabric's lineage, usage and profiler support * Python Checkstyle * Update generated TypeScript types * fix: narrow Fabric fallback from except Exception to except ProgrammingError * Addressed comments --------- Co-authored-by: Akash Verma <akashverma@Akashs-MacBook-Pro-2.local> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> * chore(ui): Add Test Case list filters while creating a bundle suite (#26293) * fix: Add Test Case list filters (Status, Test type, Table, Column) and E2E coverage - Add filters to AddTestCaseList: Status (single), Test type (single), Table (multi), Column (multi) - Use SearchDropdown for all four filters with hideCounts - Client-side filtering for Table/Column; API refetch for Status/Test type - Add AddTestCaseListFilters component and constants - Add AddTestCaseList.utils (getTableFilterOptions, getColumnFilterOptions, filterTestCasesByTableAndColumn, getSelectedOptionsFromKeys) - Unit tests: AddTestCaseList.component.test.tsx (filter tests), AddTestCaseList.utils.test.ts - E2E: TestSuite.spec.ts - flatten steps, verify/apply/clear filters in create flow Fixes https://github.com/open-metadata/openmetadata-collate/issues/3045 Made-with: Cursor * fix lint * address gitar-bot comments * fix sonar issues * address gitar-bot comments and sonar issues * minor fix * fix gitar-bot comments * use backend filter for table type * feat: added columnName parameter * feat: adde columnname parameter * feat: added colunmName argument * convert column filter to server side filter * address gitar-bot comments * minor fix * fix failing test * address sonar issues * Revert yarn.lock changes in openmetadata-ui-core-components Made-with: Cursor * address comment * show select all filter in all test case lists * address copilot comments * add hideTableFilter and columnFilter props * address comments * hide table filter for for add pipeline under table * fix failing test * fix failing tests --------- Co-authored-by: TeddyCr <teddy.crepineau@gmail.com> Co-authored-by: Shailesh Parmar <shailesh.parmar.webdev@gmail.com> * added unit tests for kafkaconnect pipeline * Add gitar fix * MINOR - Column name Length patch (#26530) * chore(bulkEndpoint): create bulk bundle suite body object * patch(columnName): remove maxLength for column name * patch(columnName): remove files from commit * patch(columnName): remove unused code * fix unit tests --------- Co-authored-by: ulixius9 <mayursingal9@gmail.com> * update alert props (#26544) * Fix: flaky domain rename data products count assertion (#26542) * Fix: flaky domain rename data products count assertion After a domain rename, the search index update for subdomain-level data products can lag behind the DB update due to async reindexing by the governance-bot. The `verifyDataProductsCount` helper was doing a one-shot `textContent()` + `toBe()` assertion that failed when the search index hadn't converged yet. Changes: - Update `verifyDataProductsCount` to accept optional `{ apiContext, domainFqn }` that uses `expect.poll()` to poll the data product search API until `hits.total.value` matches the expected count (following the same pattern used in glossary.ts, alert.ts, and other polling utilities) - Switch from one-shot `toBe()` to auto-retrying `toHaveText()` for the UI check - Pass polling options in the post-rename assertion in Domains.spec.ts Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Add HTTP status check in search API poll Check response.ok() before parsing JSON in the expect.poll callback to avoid silently treating 4xx/5xx errors as count=0. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Remove custom timeout from toHaveText assertion The expect.poll already ensures the search index has converged before the UI check, so the default Playwright timeout is sufficient. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Siddhant <siddhant@MacBook-Pro-290.local> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Refactor InputOutputPortsTab to use Accordion components and update styles (#26450) * Refactor InputOutputPortsTab to use Accordion components and update styles * addressed PR comment * fixed playwright test * addressed gitar comment and fix sonar issues * fixed overflow issue * fixed ui issues * minor fix * addressed UI fixes * py_format_check * Added test for table format without topic prefix * Removed commented code --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Karan Hotchandani <33024356+karanh37@users.noreply.github.com> Co-authored-by: Rohit Jain <60229265+Rohit0301@users.noreply.github.com> Co-authored-by: Shailesh Parmar <shailesh.parmar.webdev@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Anujkumar Yadav <anujf0510@gmail.com> Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: Akash Verma <138790903+akashverma0786@users.noreply.github.com> Co-authored-by: Akash Verma <akashverma@Akashs-MacBook-Pro-2.local> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Mayur Singal <39544459+ulixius9@users.noreply.github.com> Co-authored-by: Harsh Vador <58542468+harsh-vador@users.noreply.github.com> Co-authored-by: Harshit Shah <harshit.shah@getcollate.io> Co-authored-by: Sriharsha Chintalapani <harshach@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Mohit Yadav <105265192+mohityadav766@users.noreply.github.com> Co-authored-by: IceS2 <pablo.takara@getcollate.io> Co-authored-by: Eugenio <eugenio.donaque@getcollate.io> Co-authored-by: Pere Miquel Brull <peremiquelbrull@gmail.com> Co-authored-by: Aniket Katkar <aniketkatkar97@gmail.com> Co-authored-by: TeddyCr <teddy.crepineau@gmail.com> Co-authored-by: ulixius9 <mayursingal9@gmail.com> Co-authored-by: Sid <30566406+siddhant1@users.noreply.github.com> Co-authored-by: Siddhant <siddhant@MacBook-Pro-290.local> Co-authored-by: Suman Maharana <sumanmaharana786@gmail.com>

* * fixed kafka sink linage * fix kafka pipline linage topic to table matching * chore(ui): add sidebar navigation (open-metadata#26498) * chore(ui): add sidebar navigation * fix * Migrated CustomControls and BulkImportVersionSummary (open-metadata#26410) * Migrated CustomControls and BulkImportVersionSummary * migrated styled button component and playwright fixes * fixed unit test * fixed the bulkimportsummary modal and custom control tab item * fixed the sonar issue * addressed pr comments * fixed playwright * fixed playwright and lint issues * addressed gitar comment --------- Co-authored-by: Shailesh Parmar <shailesh.parmar.webdev@gmail.com> * refactor: update toggle component and related fields to use UT_SWITCH type (open-metadata#26425) * refactor: update toggle component and related fields to use UT_SWITCH type * addressed gitar comment * fixed unit tests * addressed PR comment * Chore(deps): Bump undici in /openmetadata-ui/src/main/resources/ui (open-metadata#26497) Bumps [undici](https://github.com/nodejs/undici) from 6.23.0 to 6.24.1. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v6.23.0...v6.24.1) --- updated-dependencies: - dependency-name: undici dependency-version: 6.24.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(ui): fix UserTeamSelectableList closing when clicking inside popover in modal (open-metadata#26502) * Remove unused `/api/v1/domains?limit=10000&fields=parent` call on every page load (open-metadata#26485) * Initial plan * Remove unused domain list API call on every page load Co-authored-by: karanh37 <33024356+karanh37@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: karanh37 <33024356+karanh37@users.noreply.github.com> * feat: migrate DeleteModal from MUI to untitledUI components (open-metadata#26461) * feat: migrate DeleteModal from MUI to untitledUI components * fixed the import * comment addressed * fix: remove unnecessary span element from DeleteModal * refactor: remove DeleteModal component and its associated files * addressed gitar comment * Added unit tests * MINOR: Informix Schema update (open-metadata#26483) * MINOR: Informix Schema update * fix * Update generated TypeScript types * Add supportdatabase * Update generated TypeScript types --------- Co-authored-by: Akash Verma <akashverma@Akashs-MacBook-Pro-2.local> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Mayur Singal <39544459+ulixius9@users.noreply.github.com> Co-authored-by: Anujkumar Yadav <anujf0510@gmail.com> * ui: make search placeholder in service main tabs dynamic (open-metadata#26511) * Revert "feat: migrate DeleteModal from MUI to untitledUI components (open-metadata#26461)" (open-metadata#26519) This reverts commit 8327d22. * Revert "refactor: update toggle component and related fields to use UT_SWITCH…" (open-metadata#26520) This reverts commit 59fe777. * fix(ui): Test suite add-test-case modal and table UX (open-metadata#26512) * fix(ui): Test suite add-test-case modal and table UX * fix footer padding * Add eslint-plugin-playwright enforcement with CI check (open-metadata#26494) * Add eslint-plugin-playwright enforcement with CI check Add eslint-plugin-playwright to catch common Playwright anti-patterns automatically. 13 rules configured in two tiers: - Error (blocks CI): no-networkidle, no-page-pause, no-focused-test - Warn (tracks debt): missing-playwright-await, no-wait-for-timeout, no-force-option, no-element-handle, no-eval, no-skipped-test, prefer-web-first-assertions, no-useless-await, no-wait-for-selector, valid-expect Changes: - Install eslint-plugin-playwright, configure rules in eslint.config.mjs - Add yarn lint:playwright script - Repurpose ui-checkstyle.yml workflow to run Playwright lint on PRs - Fix last networkidle usage in ClassificationConditionalRendering - Remove stale eslint-disable comments for undefined rules - Update PLAYWRIGHT_DEVELOPER_HANDBOOK with ESLint Enforcement section - Update playwright, writing-playwright-tests, and playwright-validation skills to reference lint check Current: 0 errors, 1657 warnings (CI passes cleanly) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix CodeQL cache poisoning alert: use pull_request instead of pull_request_target Switch from pull_request_target to pull_request since this workflow only runs yarn lint:playwright — no secrets or write permissions needed. This eliminates the untrusted code execution risk flagged by CodeQL. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix all 1657 Playwright ESLint warnings across 190 files Resolve every playwright lint rule violation to enforce test quality: - no-wait-for-selector (1290): replace page.waitForSelector() with locator.waitFor() - no-wait-for-timeout (130): replace hardcoded waits with event-driven alternatives - prefer-web-first-assertions (61): use toHaveText/toBeVisible/toHaveValue - no-force-option (51): remove { force: true } bypassing actionability checks - missing-playwright-await (40): add await to fire-and-forget assertions - no-skipped-test (28): acknowledge skipped tests with eslint-disable reasons - no-eval (11): replace page.$eval with locator APIs - no-element-handle (10): replace page.$() with page.locator() - no-useless-await (8): remove await from synchronous operations - valid-expect (4): add matchers to bare expect() calls - no-networkidle (2): replace networkidle with domcontentloaded Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove unnecessary ANTLR install and add --frozen-lockfile to CI - Remove Install Antlr4 CLI step from playwright-lint job (not needed for ESLint, saves 10-30s and avoids external network dependency) - Add --frozen-lockfile to yarn install for reproducible CI builds Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Restore ANTLR CLI install — required by yarn postinstall script yarn install triggers build-check → js-antlr which needs antlr4 CLI. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix trivially-true assertion in special character search test Remove `(await tableRows.count()) >= 0` which is always true since count() never returns negative. The assertion now properly validates that either the table or empty state is visible after searching. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix strict mode violations: add .first() to multi-element waitFor calls The no-wait-for-selector conversion (waitForSelector → locator.waitFor) introduced strict mode violations. Playwright's Locator API throws when waitFor() matches multiple elements, unlike the old waitForSelector API. Key patterns fixed: - getByTestId('loader').waitFor() — multiple loaders on page - getByTestId('select-owner-tabs').getByTestId('loader') — tab loaders - locator('.ant-skeleton-active/content').waitFor() — multiple skeletons - locator('table/thead th').waitFor() — multiple tables - getByTestId('side-panel-classification') — multiple panels - locator('.ant-select-dropdown:visible') — multiple dropdowns - locator('.ant-popover').waitFor() — multiple popovers Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix strict mode violation in incidentManager assignee/owner-link The getByTestId('assignee').getByTestId('owner-link') locator resolves to 15 elements in the incident manager table (one per row). Adding .first() matches the original waitForSelector semantics. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix test failures from lint conversions: proper waits and retry logic - GlossaryPermissions: add waitForAllLoadersToDisappear after page nav - GlossaryP3Tests: restore waits for special char search + error state - GlossaryStatusFilterLargeDataset: restore waitForTimeout for filter state settling (no reliable DOM element to wait for) - AutoPilot: use waitForAllLoadersToDisappear instead of .first() to ensure ALL loaders are gone, increase banner timeout to 60s - importUtils: use expect().toHaveCount(0) for scoped multi-element loader/skeleton waits instead of waitForSelector or .first() - ColumnBulkOperations: increase response timeout, add retry polling for empty state verification - DomainDataProductsWidgets: add poll-based wait for DOM update after asset removal instead of removed waitForTimeout - customizeLandingPage: scope widget click to dialog to avoid matching stale elements on the page behind the modal Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Restore force:true where genuinely needed with eslint-disable comments The no-force-option ESLint rule removal broke tests where force was required for Ant Select comboboxes (selected item overlay covers input), popover triggers (partially obstructed by animation), data grid buttons (covered by overlay), and drag-and-drop (row hover overlays). Each restoration includes an eslint-disable-line comment explaining why force is necessary. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Stabilize 4 flaky tests with retry wrappers and proper waits - DataContractsSemanticRules: Wrap reload + status assertions in expect().toPass() to handle async backend contract validation - DataContracts: Increase timeout on dynamically rendered row filter and column text assertions that contain UUID-suffixed names - Customproperties-part2: Wrap user search-and-select loop in expect().toPass() retry to handle search dropdown rendering races - UserProfileOnlineStatus: Add profile render wait, navigation completion guard, and increased badge visibility timeout Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Replace .first().waitFor loader pattern with waitForAllLoadersToDisappear The pattern `page.getByTestId('loader').first().waitFor({ state: 'detached' })` only waits for the FIRST loader element to detach. When multiple loaders exist (nested components, tabs, popovers), this causes tests to proceed before the page is fully loaded — the root cause of ~18 flaky tests. Replaced ~500 occurrences across 103 files with the correct `waitForAllLoadersToDisappear(page)` which uses `expect(loaders).toHaveCount(0)` to wait for ALL loaders to disappear. Scoped loader waits (e.g., within select-owner-tabs, test-case-container, tags-container) are intentionally preserved since they correctly target a specific container's single loader. Also fixes UserProfileOnlineStatus.spec.ts: - Added createOrFetchUser helper for idempotent user creation on retries - Added afterAll cleanup for test users - Replaced waitForURL with redirectToHomePage for navigation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Karan Hotchandani <33024356+karanh37@users.noreply.github.com> * [Fix-25563] - Issue in Search Entity By Key (open-metadata#26482) * Fix Issue Entity Not found , entity missing from search * Fix Tests * Fix Broken relationship issue for upstreamEntityRelationship * Add Exponential Retry * Remove Entity Not found from query * Address Reciew Comments * Address more review * Fix Missing Columns Index * Fix Join add stats * Column stats and Merged Main * Add separate custom bulk processor for column * Fix reindex job falsely killed after 1 hour by orphan monitor The OrphanJobMonitor uses job.updatedAt as a liveness signal, but updatedAt was only set during state transitions (READY, RUNNING), never refreshed during processing. After 10 minutes the job appeared orphaned; at the 1-hour recovery window it was force-failed. Fix: touch updatedAt alongside the lock refresh (every 60s) so the staleness check stays satisfied while the coordinator is alive. * Set Failure callback for columnBulkProcessor * fix review comments * address review comments from claude * Review Mocked tests * Address review comments. Both fixed: 1. retryOnConflict(3) restored on all 4 call sites — updateEntity and upsertDocument in both ElasticSearchEntityManager and OpenSearchEntityManager. This handles shard-level version conflicts independently from the 429 retry logic in SearchRetryUtil. 2. drainPendingColumnFutures race fixed in both bulk sinks — replaced iterate + clear() with poll() loop, which atomically removes each element from the deque so no concurrently-added futures can be lost * Get proper error message from Elastic and OpenSearch * Fix Breaking Test * MINOR: Port py-tests improvements to py-tests-postgres workflow (open-metadata#26517) Apply the same structural improvements from the py-tests workflow: - Add integration test sharding (shard-1/shard-2) for parallelism - Replace `make run_python_tests` with nox integration-tests session - Add explicit timeout-minutes (180) and descriptive job name - Remove unnecessary fetch-depth: 0 from checkout - Normalize indentation to 2-space with proper YAML style * Use context to enhance recognition by default (open-metadata#25856) * Implement custom context enhancement for Presidio recognizers Presidio's default context enhancement relies heavily on NLP and often fails when analyzing individual values rather than full text. This implements a custom context enhancement that: - Boosts recognizer scores to MAX when context keywords match - Applies a minimum score threshold (0.3) before enhancement - Skips already-enhanced results to prevent double-boosting - Introduces a decorator pattern for composing recognizer enhancements - Adds eager_us_bank_recognizer with higher base scores for better results The enhancement works by checking if any context words from the recognizer match the provided context list, then boosting the confidence score to maximum and setting the IS_SCORE_ENHANCED_BY_CONTEXT_KEY metadata flag. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Integrate context enhancement into recognizer factory Updates PresidioRecognizerFactory to apply the new decorator pattern: - All recognizers now use enhance_using_context decorator - Confidence threshold filtering applied via filter_enhanced_results_below_threshold - Decorators composed using decorate_recognizer for clean application - Context passed to PatternRecognizer during creation This ensures all enabled recognizers benefit from custom context enhancement while maintaining backward compatibility with confidence thresholds. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Add migration to update PII tag recognizers with enhanced configs Adds a v1.1.22 migration that updates existing PII tags with improved recognizer configurations featuring context keywords and optimized patterns. Changes: - Add patchRecognizers method in CollectionDAO for updating tag recognizers - Implement setRecognizersForSensitiveTags in MigrationUtil to load and apply recognizer configs from piiTagsWithRecognizers.json - Update piiTagsWithRecognizers.json with context keywords for better classification accuracy - Execute migration as post-DDL script for both MySQL and PostgreSQL This migration ensures existing deployments benefit from the improved context enhancement logic without manual reconfiguration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Fix potential NPE and type mismatch in migration utility Addresses code review feedback: 1. Fix potential NullPointerException in setRecognizersForSensitiveTags - Use Boolean.TRUE.equals() instead of auto-unboxing for nullable Boolean - Prevents NPE when autoClassificationEnabled is absent from JSON - Follows existing pattern from v1120/MigrationUtil.java 2. Fix Boolean vs boolean type mismatch in updateTagRecognizers - Change isForceMigration parameter from boxed Boolean to primitive boolean - Matches caller signature and eliminates latent NPE risk - Maintains consistency across method signatures 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Add context to NHSRecognizer * Fix typing * Fix broken unit tests * Fix broken integration test --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Pere Miquel Brull <peremiquelbrull@gmail.com> * Chore(UI): Remove tags customization option (open-metadata#26514) * Add regenerate-bot-tokens operation for JWT key rotation (open-metadata#26477) * Add regenerate-bot-tokens operation for JWT key rotation Add a new `regenerate-bot-tokens` subcommand to OpenMetadataOperations that regenerates JWT tokens for all bot users. This is needed when rotating JWT signing keys or changing the cluster name (e.g., during disaster recovery from POV to PROD). The command: - Iterates through all non-deleted bots with pagination - Regenerates JWT tokens only for bots using JWT authentication - Skips bots without associated users or non-JWT auth mechanisms - Displays results in an ASCII table with status per bot Closes open-metadata/openmetadata-collate#3157 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix review: add --expiry CLI parameter and null-guard paging - Token expiry is now a CLI parameter (--expiry) defaulting to Unlimited, so operators can choose OneHour, One, Seven, Thirty, Sixty, Ninety, or Unlimited when regenerating - Add null guard on getPaging() to prevent NPE on empty result sets Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Document regenerate-bot-tokens expiry values in help output Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Move bot token regeneration logic to server API Move the token regeneration logic from the ops CLI into a new REST endpoint PUT /v1/users/regenerateBotTokens (admin-only). The ops command now calls the server API via HTTP, following the same pattern as deploy-pipelines. This keeps business logic in the server and the ops CLI as a thin HTTP client. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Revert server API approach, use direct DB access for token regeneration After JWT key rotation, all existing bot tokens are invalid — including the ingestion-bot token needed to authenticate against the server API. This command must operate directly on the database to recover from that state. Added a doc comment explaining the reasoning. Also reverts the UserResource endpoint added in the previous commit. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix compilation: use fully-qualified ResultList to match existing pattern Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix botUser always null: fetch each bot individually via getByName listAll/listAfter use setFieldsInBulk which only calls registered fieldFetchers (tags, owners, etc.) — not the entity-specific setFields override. BotRepository.setFields populates botUser via a relationship lookup, but this is never called in bulk listing. Fetch each bot individually with getByName which triggers setFields properly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add integration tests for regenerate-bot-tokens operation Tests cover token regeneration producing new tokens, respecting expiry parameters, and handling multiple bots independently. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix flaky test: use different expiries to guarantee distinct tokens Unlimited tokens generated in the same second produce identical JWTs (same iat, null exp). Changed test to use different expiry values so the tokens are guaranteed to differ. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * format --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> * Fix open-metadata#2730: Add tempLineageTables field to lineage details (open-metadata#26487) * Fix open-metadata#2730: Lineage Add Temp Node Support * missing sql file * Update generated TypeScript types * Update generated TypeScript types * address guitar commens --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> * Feature: Fabric's lineage, usage and profiler support (open-metadata#26373) * Feature: Fabric's lineage, usage and profiler support * Python Checkstyle * Update generated TypeScript types * fix: narrow Fabric fallback from except Exception to except ProgrammingError * Addressed comments --------- Co-authored-by: Akash Verma <akashverma@Akashs-MacBook-Pro-2.local> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> * chore(ui): Add Test Case list filters while creating a bundle suite (open-metadata#26293) * fix: Add Test Case list filters (Status, Test type, Table, Column) and E2E coverage - Add filters to AddTestCaseList: Status (single), Test type (single), Table (multi), Column (multi) - Use SearchDropdown for all four filters with hideCounts - Client-side filtering for Table/Column; API refetch for Status/Test type - Add AddTestCaseListFilters component and constants - Add AddTestCaseList.utils (getTableFilterOptions, getColumnFilterOptions, filterTestCasesByTableAndColumn, getSelectedOptionsFromKeys) - Unit tests: AddTestCaseList.component.test.tsx (filter tests), AddTestCaseList.utils.test.ts - E2E: TestSuite.spec.ts - flatten steps, verify/apply/clear filters in create flow Fixes https://github.com/open-metadata/openmetadata-collate/issues/3045 Made-with: Cursor * fix lint * address gitar-bot comments * fix sonar issues * address gitar-bot comments and sonar issues * minor fix * fix gitar-bot comments * use backend filter for table type * feat: added columnName parameter * feat: adde columnname parameter * feat: added colunmName argument * convert column filter to server side filter * address gitar-bot comments * minor fix * fix failing test * address sonar issues * Revert yarn.lock changes in openmetadata-ui-core-components Made-with: Cursor * address comment * show select all filter in all test case lists * address copilot comments * add hideTableFilter and columnFilter props * address comments * hide table filter for for add pipeline under table * fix failing test * fix failing tests --------- Co-authored-by: TeddyCr <teddy.crepineau@gmail.com> Co-authored-by: Shailesh Parmar <shailesh.parmar.webdev@gmail.com> * added unit tests for kafkaconnect pipeline * Add gitar fix * MINOR - Column name Length patch (open-metadata#26530) * chore(bulkEndpoint): create bulk bundle suite body object * patch(columnName): remove maxLength for column name * patch(columnName): remove files from commit * patch(columnName): remove unused code * fix unit tests --------- Co-authored-by: ulixius9 <mayursingal9@gmail.com> * update alert props (open-metadata#26544) * Fix: flaky domain rename data products count assertion (open-metadata#26542) * Fix: flaky domain rename data products count assertion After a domain rename, the search index update for subdomain-level data products can lag behind the DB update due to async reindexing by the governance-bot. The `verifyDataProductsCount` helper was doing a one-shot `textContent()` + `toBe()` assertion that failed when the search index hadn't converged yet. Changes: - Update `verifyDataProductsCount` to accept optional `{ apiContext, domainFqn }` that uses `expect.poll()` to poll the data product search API until `hits.total.value` matches the expected count (following the same pattern used in glossary.ts, alert.ts, and other polling utilities) - Switch from one-shot `toBe()` to auto-retrying `toHaveText()` for the UI check - Pass polling options in the post-rename assertion in Domains.spec.ts Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Add HTTP status check in search API poll Check response.ok() before parsing JSON in the expect.poll callback to avoid silently treating 4xx/5xx errors as count=0. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Remove custom timeout from toHaveText assertion The expect.poll already ensures the search index has converged before the UI check, so the default Playwright timeout is sufficient. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Siddhant <siddhant@MacBook-Pro-290.local> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Refactor InputOutputPortsTab to use Accordion components and update styles (open-metadata#26450) * Refactor InputOutputPortsTab to use Accordion components and update styles * addressed PR comment * fixed playwright test * addressed gitar comment and fix sonar issues * fixed overflow issue * fixed ui issues * minor fix * addressed UI fixes * py_format_check * Added test for table format without topic prefix * Removed commented code --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Karan Hotchandani <33024356+karanh37@users.noreply.github.com> Co-authored-by: Rohit Jain <60229265+Rohit0301@users.noreply.github.com> Co-authored-by: Shailesh Parmar <shailesh.parmar.webdev@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Anujkumar Yadav <anujf0510@gmail.com> Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: Akash Verma <138790903+akashverma0786@users.noreply.github.com> Co-authored-by: Akash Verma <akashverma@Akashs-MacBook-Pro-2.local> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Mayur Singal <39544459+ulixius9@users.noreply.github.com> Co-authored-by: Harsh Vador <58542468+harsh-vador@users.noreply.github.com> Co-authored-by: Harshit Shah <harshit.shah@getcollate.io> Co-authored-by: Sriharsha Chintalapani <harshach@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Mohit Yadav <105265192+mohityadav766@users.noreply.github.com> Co-authored-by: IceS2 <pablo.takara@getcollate.io> Co-authored-by: Eugenio <eugenio.donaque@getcollate.io> Co-authored-by: Pere Miquel Brull <peremiquelbrull@gmail.com> Co-authored-by: Aniket Katkar <aniketkatkar97@gmail.com> Co-authored-by: TeddyCr <teddy.crepineau@gmail.com> Co-authored-by: ulixius9 <mayursingal9@gmail.com> Co-authored-by: Sid <30566406+siddhant1@users.noreply.github.com> Co-authored-by: Siddhant <siddhant@MacBook-Pro-290.local> Co-authored-by: Suman Maharana <sumanmaharana786@gmail.com>

ulixius9 added 2 commits March 13, 2026 20:14

Fix #2730: Lineage Add Temp Node Support

3f22b4f

missing sql file

0b81e5b

ulixius9 requested a review from a team as a code owner March 13, 2026 14:48

github-actions Bot added Ingestion safe to test Add this label to run secure Github workflows on PRs labels Mar 13, 2026

Update generated TypeScript types

d783d25

github-actions Bot requested a review from a team as a code owner March 13, 2026 14:52

gitar-bot Bot reviewed Mar 13, 2026

View reviewed changes

Comment thread ingestion/src/metadata/ingestion/lineage/sql_lineage.py

ulixius9 and others added 2 commits March 14, 2026 07:18

Merge branch 'main' into issue-2730-temp-lineage-tables

49fcad9

Update generated TypeScript types

d2c9ee0

chirag-madlani previously approved these changes Mar 16, 2026

View reviewed changes

ulixius9 and others added 2 commits March 16, 2026 14:43

Merge branch 'main' into issue-2730-temp-lineage-tables

4b769df

address guitar commens

b7463aa

ulixius9 dismissed chirag-madlani’s stale review via b7463aa March 16, 2026 09:22

ulixius9 temporarily deployed to test March 16, 2026 09:31 — with GitHub Actions Inactive

ulixius9 had a problem deploying to test March 16, 2026 09:31 — with GitHub Actions Failure

ulixius9 temporarily deployed to test March 16, 2026 09:31 — with GitHub Actions Inactive

ulixius9 merged commit d38423f into main Mar 16, 2026
42 of 46 checks passed

ulixius9 deleted the issue-2730-temp-lineage-tables branch March 16, 2026 16:26

Vishnuujain mentioned this pull request Jun 2, 2026

fix(mcp): remove temp-table lineage refs on 1.12.10 (schema not backported) #28644

Merged

Navigation Menu

Uh oh!

Fix #2730: Add tempLineageTables field to lineage details - #26487

Fix #2730: Add tempLineageTables field to lineage details#26487
ulixius9 merged 7 commits into
mainfrom
issue-2730-temp-lineage-tables

ulixius9 commented Mar 13, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Mar 13, 2026

Uh oh!

Uh oh!

github-actions Bot commented Mar 13, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Mar 13, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Mar 13, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Mar 14, 2026

Uh oh!

github-actions Bot commented Mar 14, 2026 •

edited

Loading

Uh oh!

gitar-bot Bot commented Mar 16, 2026

Uh oh!

sonarqubecloud Bot commented Mar 16, 2026

Uh oh!

sonarqubecloud Bot commented Mar 16, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

ulixius9 commented Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

github-actions Bot commented Mar 13, 2026

✅ TypeScript Types Auto-Updated

Uh oh!

Uh oh!

github-actions Bot commented Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🛡️ TRIVY SCAN RESULT 🛡️

Target: openmetadata-ingestion-base-slim:trivy (debian 12.13)

Vulnerabilities (257)

🛡️ TRIVY SCAN RESULT 🛡️

Target: Java

Vulnerabilities (37)

🛡️ TRIVY SCAN RESULT 🛡️

Target: Node.js

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Python

Vulnerabilities (9)

🛡️ TRIVY SCAN RESULT 🛡️

Target: /etc/ssl/private/ssl-cert-snakeoil.key

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/extended_sample_data.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/lineage.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data.json

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data_aut.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage.json

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage_aut.yaml

No Vulnerabilities Found

Uh oh!

github-actions Bot commented Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🛡️ TRIVY SCAN RESULT 🛡️

Target: openmetadata-ingestion:trivy (debian 12.12)

Vulnerabilities (4)

🛡️ TRIVY SCAN RESULT 🛡️

Target: Java

Vulnerabilities (38)

🛡️ TRIVY SCAN RESULT 🛡️

Target: Node.js

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Python

Vulnerabilities (25)

🛡️ TRIVY SCAN RESULT 🛡️

Target: usr/bin/docker

Vulnerabilities (3)

🛡️ TRIVY SCAN RESULT 🛡️

Target: /etc/ssl/private/ssl-cert-snakeoil.key

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /home/airflow/openmetadata-airflow-apis/openmetadata_managed_apis.egg-info/PKG-INFO

No Vulnerabilities Found

Uh oh!

github-actions Bot commented Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔴 Playwright Results — 2 failure(s), 24 flaky

ulixius9 commented Mar 13, 2026 •

edited

Loading

github-actions Bot commented Mar 13, 2026 •

edited

Loading

Target: `openmetadata-ingestion-base-slim:trivy (debian 12.13)`

Target: `Java`

Target: `Node.js`

Target: `Python`

Target: `/etc/ssl/private/ssl-cert-snakeoil.key`

Target: `/ingestion/pipelines/extended_sample_data.yaml`

Target: `/ingestion/pipelines/lineage.yaml`

Target: `/ingestion/pipelines/sample_data.json`

Target: `/ingestion/pipelines/sample_data.yaml`

Target: `/ingestion/pipelines/sample_data_aut.yaml`

Target: `/ingestion/pipelines/sample_usage.json`

Target: `/ingestion/pipelines/sample_usage.yaml`

Target: `/ingestion/pipelines/sample_usage_aut.yaml`

github-actions Bot commented Mar 13, 2026 •

edited

Loading

Target: `openmetadata-ingestion:trivy (debian 12.12)`

Target: `Java`

Target: `Node.js`

Target: `Python`

Target: `usr/bin/docker`

Target: `/etc/ssl/private/ssl-cert-snakeoil.key`

Target: `/home/airflow/openmetadata-airflow-apis/openmetadata_managed_apis.egg-info/PKG-INFO`

github-actions Bot commented Mar 13, 2026 •

edited

Loading

github-actions Bot commented Mar 14, 2026 •

edited

Loading