potiuk opened a new pull request, #71718: URL: https://github.com/apache/airflow/pull/71718
`uv lock --upgrade` in `breeze ci upgrade` can move `datamodel-code-generator`, whose version is stamped into the header of every file it generates. The two codegen hooks are gated on the execution and core API sources, which an upgrade run never touches, so they stay dormant while the automation commits — and the next CI run, which invokes them with `--all-files`, regenerates the headers and fails the static checks job on the upgrade PR itself. That is what happened on #71590 (0.71.0 → 0.72.4): `Static checks` was the only failing job in the run, and the whole diff was three `# version:` comments. Regenerating them is tied to the lock step here so the upgrade PR comes out self-consistent. No unit test: the step list lives inside the `ci upgrade` click command and its sibling entries have no coverage either, so this is a declarative addition to untested orchestration. The verification is the next scheduled upgrade run producing a green PR. related: #71590 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5) Generated-by: Claude Code (Opus 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
