chore(release): Prepare Branch for release 1.13.3

[ShaileshParmar11]

Bumps the charts to 1.13.3. Same shape as #525 (1.13.2) — 8 lines across the same 5 files.

Why

The release workflow was dispatched today and failed:

Error: error creating GitHub release openmetadata-1.13.2:
POST /repos/open-metadata/openmetadata-helm-charts/releases:
422 Validation Failed [{Resource:Release Field:tag_name Code:already_exists}]

main was still at 1.13.2 (last commit 96bb1acc, the 1.13.2 prep), so chart-releaser repackaged 1.13.2, tried to create a release for a tag published the day before, and exited 1. It never reached 1.13.3 — the version bump had simply not been made.

Changes

File	Change
.version	1.13.2 → 1.13.3
charts/openmetadata/Chart.yaml	version, appVersion, artifacthub.io/images server tag
charts/openmetadata/README.md	image.tag table row
charts/deps/Chart.yaml	version, appVersion
charts/deps/values.yaml	airflow tag

Verified there are no remaining 1.13.2 references anywhere in the tree.

Images confirmed published

Both tags the charts point at exist on Docker Hub:

• openmetadata/server:1.13.3 — 200
• openmetadata/ingestion:1.13.3 — 200

After merge

Re-run Release Open Metadata Charts to publish openmetadata-1.13.3 and openmetadata-dependencies-1.13.3. Confirm with:

curl -s https://helm.open-metadata.org/index.yaml | grep -c 'version: 1.13.3'

Expect 2.

This unblocks the sandbox, which is currently failing to sync — k8s-manifests#363 already moved sandbox-omd to targetRevision: 1.13.3, so Argo is reporting:

ComparisonError: chart "openmetadata" version "1.13.3" not found in https://helm.open-metadata.org/

k8s-manifests#364 (the matching dependencies bump) is waiting on the same thing.

Unrelated suggestion

Dispatching the release workflow without a version bump will always 422 against the previous release rather than reporting "nothing to release". chart-releaser's skip_existing option would turn that into a no-op and make the real problem obvious. Happy to open that separately.

🤖 Generated with Claude Code

[ShaileshParmar11]

Superseded by #526, which the Create Release Branch workflow opened and which is now merged. My branch is byte-identical to main — zero diff — so this is a no-op.

I hand-authored this before spotting that the repo automates it via git-create-release-branch.yml. The correct route is dispatching that workflow with the version, which is what happened at 11:01. Closing.