Move preview-to-enabled migrations from 1.11.13 to 1.13.0

[pmbrull]

Summary

• Move the preview → enabled app property migration SQL files from bootstrap/sql/migrations/native/1.11.13/ to bootstrap/sql/migrations/native/1.13.0/ since this change targets the next major release, not a patch release
• Removes the now-empty 1.11.13 migration directory

PR #26170 revert verification

Verified that PR #26170 was properly reverted on release branches:

Repo	Branch	Status
OpenMetadata	release/1.12.2	Properly reverted (commit 51c9b6af)
OpenMetadata	release/1.11.13	Branch does not exist — N/A
Collate	release/1.12.2	Properly reverted (commit 29e13874)
Collate	release/1.11.13	Branch does not exist — N/A

Test plan

• Verify bootstrap/sql/migrations/native/1.11.13/ no longer exists
• Verify bootstrap/sql/migrations/native/1.13.0/mysql/schemaChanges.sql contains the preview-to-enabled migration
• Verify bootstrap/sql/migrations/native/1.13.0/postgres/schemaChanges.sql contains the preview-to-enabled migration

[gitar-bot]

🔍 CI failure analysis for c9b7a58: All CI failures are unrelated to this PR's changes (SQL migration file moves between directories). The failures are pre-existing infrastructure/flakiness issues.

Issue

Three separate CI failures observed, all unrelated to this PR's changes (which only move SQL migration files between bootstrap/sql/migrations/native/1.11.13/ and bootstrap/sql/migrations/native/1.13.0/).

---

Failure 1: playwright-ci-postgresql (4, 6) — Browser Stability / Test Flakiness

Root Cause: Browser/page closure during Playwright E2E test execution, causing cascading timeouts across multiple test suites.

Key errors:

Entity.spec.ts:2137 › Table › Set & update column-level custom property
  Test timeout 180000ms exceeded
  page.waitForResponse failed: "Target page, context or browser has been closed"

Customproperties-part2.spec.ts:187 — API timeout waiting for /api/v1/search/query
DataContractsSemanticRules.spec.ts:913 — page.goto timeout navigating to localhost:8585
Domains.spec.ts:229 — page.goto timeout navigating to localhost:8585
PersonaFlow.spec.ts:498 — stale persona ID in test data

These are pre-existing infrastructure instability issues (browser crashes, backend service slowness) with no relation to SQL migration changes.

---

Failure 2: integration-tests-mysql-elasticsearch — Async Vector Embedding Race Condition

Root Cause: Race condition in test teardown between async VectorEmbeddingHandler processing and resource cleanup:

org.openmetadata.service.search.vector.client.DjlEmbeddingClient$EmbeddingGenerationException:
  Unexpected error during DJL batch embedding generation
Caused by: java.lang.IllegalStateException: NDManager has been closed already.

java.lang.RuntimeException: Connection pool shut down
Caused by: java.lang.IllegalStateException: Connection pool shut down
    at org.apache.hc.core5.pool.StrictConnPool.lease(StrictConnPool.java:175)

The async VectorEmbeddingHandler is not unregistered before teardown, causing async threads to use already-closed resources. This is a pre-existing flakiness issue.

---

Failure 3: maven-sonarcloud-ci — SonarCloud Project Not Found

Root Cause: SonarCloud scanner failed to find the openmetadata-java-client project:

[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.10.0.2594:sonar
  on project openmetadata-java-client: Project not found. Please check the 'sonar.projectKey'
  and 'sonar.organization' properties, the 'SONAR_TOKEN' environment variable, or contact the
  project administrator to check the permissions of the user the token belongs to

This indicates an expired/invalid SONAR_TOKEN, missing SonarCloud project configuration, or permissions issue — an infrastructure concern unrelated to this PR.

---

All three failures are pre-existing infrastructure or flakiness issues. None are related to moving SQL migration files between version directories.

Code Review ✅ Approved

Moves preview-to-enabled migrations from version 1.11.13 to 1.13.0, consolidating migration timing for the ingestion system. No issues found.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

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}