RehanAhmad25 commented on PR #70072: URL: https://github.com/apache/airflow/pull/70072#issuecomment-5041035190
@ephraimbuddy Completed the migration work discussed above and force-pushed this branch. A couple of local pre-push checks blocked the push at first, both unrelated to this PR, more on that below, so I bypassed them locally to get this up. **What changed:** added the migration, changing `dag_run.created_dag_version_id`'s FK from `ON DELETE SET NULL` to `ON DELETE RESTRICT` (mirrors migration `0072`, which did the same for `task_instance.dag_version_id`). Updated the model and `REVISION_HEADS_MAP` to match. Verified locally with a full `db migrate` → `db downgrade` → `db migrate` round-trip, and the existing tests for this fix still pass. **Why the force-push:** I rebased onto current `main` to pick up the latest history and get a clean base for the new migration, rather than merging. **The local checks that blocked me:** `check-provider-yaml-valid` failing on `providers/common/ai/provider.yaml` (a missing `AWSToolset` registration), and `ktlint` failing because I don't have a local Java runtime for the JVM/TS SDK files that came in via the rebase. Neither touches anything in this diff, both are pre-existing on `main`. If CI shows either red, that's why. Could someone approve the workflows so CI can run on this? Happy to address anything it turns up. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
