henry3260 opened a new pull request, #72634: URL: https://github.com/apache/airflow/pull/72634
## Why #71379 made `DagRunAssetReference.start_date` nullable so asset-event endpoints no longer 500 when a created Dag run is still queued. The change was never registered with the Execution API versioning layer, so the server sends `"start_date": null` to every client. All released Task SDKs (1.1.x through 1.3.x) still require `start_date` and use `extra="forbid"`, so `GET /asset-events/by-asset` and `/by-asset-alias` fail client-side with a `ValidationError` whenever an event created a queued run. ## What - Add `run_after` to `DagRunAssetReference` and register `MakeCreatedDagRunStartDateNullable` in the head version (`2026-10-30`). For older clients the converter fills a null `start_date` with `run_after` and strips `run_after`, mirroring the existing `DagRun` fallback in `MakeDagRunStartDateNullable`. - Regenerate task-sdk datamodels, the supervisor schema snapshot and `ts-sdk` types. - Tests: new `versions/v2026_06_30/test_asset_events.py` covers both endpoints for a queued and a started run (fails without the fix); head test now asserts `run_after` is present; task-sdk client test payload gains `run_after`. related:#71379 ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Fable 5.1) -- 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]
