github-actions[bot] opened a new pull request, #75105: URL: https://github.com/apache/airflow/pull/75105
* Reject reserved serialization keys in Dag run conf XCom values and Human-in-the-loop params already reject keys reserved by the serialization format. Apply the same check to Dag run conf where it enters through the REST API (trigger, asset materialize, backfill) and the Execution API trigger route. A triggerer Deadline callback whose context still holds reserved keys in either encoding is marked failed instead of queued, so the scheduler loop keeps handling other deadlines. Generated-by: Claude Opus 5 following the guidelines at https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions * Move the conf reserved-key check next to find_reserved_keys The backfill and Execution API datamodels import it too, so keeping it in dag_run.py made two unrelated models depend on the Dag run module for a shared validation helper. (cherry picked from commit 325360c2b9252d9b0fe707f2fdcc6b6882504ca8) Co-authored-by: Jarek Potiuk <[email protected]> Generated-by: Claude Opus 5 -- 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]
