Skip to content

chore: add release notes for 1.13.3 - #363

Merged
ShaileshParmar11 merged 1 commit into
mainfrom
release-notes-1.13.3
Jul 31, 2026
Merged

chore: add release notes for 1.13.3#363
ShaileshParmar11 merged 1 commit into
mainfrom
release-notes-1.13.3

Conversation

@ShaileshParmar11

Copy link
Copy Markdown
Contributor

Adds the 1.13.3 release notes, following the structure of #357 (1.13.2).

Changes

  • snippets/releases/1.13.3.mdx (new) — 1.13.3 release notes.
  • snippets/releases/latest.mdx — replaced with the 1.13.3 content.
  • v1.13.x/releases/all-releases.mdx — imports 1.13.2.mdx as ReleaseNotes16 (demoted from latest), renders it directly under <ReleaseNotes />, and bumps the upgrade card to 1.13.3.
  • v2.0.x-SNAPSHOT/releases/all-releases.mdx — same import/ordering change. Upgrade card left at 2.0.0.

Content

Derived from 1.13.2-release...1.13.3-release (19 commits). Seven are user-facing; the rest are Playwright/test fixes, a CustomizePageUtils refactor, a reverted-and-re-cherry-picked intake-forms change, and release chores.

Area Entry
Connectors & Ingestion Snowflake FK collisions across tables sharing a constraint name (#30473)
Data Governance & Quality Data contracts stuck at Running (#30531) · poisoned governance trigger filters (5963637b) · soft-deleted owners on Test Suite (#30520) · intake form formFields (#30614)
Platform Skip notification recipients without contact info (#30518)
UI Tag/Glossary dropdowns in Column Bulk Operations drawer (#30634)

Notes for reviewers

  • The intake-forms entry is backend only on this line — the UI half of #30614 was reverted on 1.13 because it depends on ui-core-components APIs not present there. Called out in the entry text.
  • The governance trigger-filter fix landed as a direct commit with no PR, so it links to the commit.
  • 1.13.3 ships two migrations (v1133 trigger-filter sanitizer, intake-form formFields backfill). 1.13.2's notes carried no upgrade section, so none was added here — say the word if you'd like one.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jul 31, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
openmetadata 🟢 Ready View Preview Jul 31, 2026, 9:47 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@kiran1287

Copy link
Copy Markdown
Contributor

✅ Release notes verified — no issues found

Fact-checked all 6 PR references + 1 direct commit against open-metadata/OpenMetadata, including confirming each fix landed in the 1.13.3 release branch (not just merged to main):

  • Snowflake FK collision fix (#30473) — (fk_name, table_name) keying and 400 Invalid column name match exactly
  • Data contracts stuck at Running (#30531) — confirmed regression from 1.13.0, fix description matches precisely
  • Governance trigger-filter sanitizer (5963637b) — direct commit verified, correctly cited as a commit link (no PR exists)
  • Soft-deleted Test Suite owners (#30520) — array item index is out of range / includeRelations fix matches exactly
  • Intake form formFields (#30614) — note correctly scopes this down to the backend-only piece; confirmed via a separate "cherry-pick backend changes from #30614 onto 1.13" commit that the UI half genuinely wasn't backported
  • Notification recipients (#30518) — matches "resolved individually, matching the webhook path" almost verbatim
  • Tag/Glossary dropdowns (#30634) — matches "focus containment... swallow all clicks" almost verbatim
  • Release date (31st July 2026) confirmed against the actual 1.13.3-release tag

Structural checks:

  • snippets/releases/1.13.2.mdx (newly-archived entry) is byte-identical to the old latest.mdx content — nothing lost in the demotion
  • Import/insertion order in both all-releases.mdx files matches the established convention
  • v2.0.x-SNAPSHOT upgrade card correctly left at 2.0.0 (independent version line)
  • No missing 1.13-release.mdx archive page — none exists yet by design (only 1.8–1.12 have dedicated pages)

Writing standards:

  • "You can find the GitHub release here." matches the 1.13.2.mdx precedent word-for-word
  • Bullet spacing and category emoji consistent with the prior release
  • Summary paragraph accurately reflects all four represented areas

Good to merge.

@ShaileshParmar11
ShaileshParmar11 merged commit 25c6190 into main Jul 31, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants