potiuk opened a new pull request, #70670:
URL: https://github.com/apache/airflow/pull/70670

   The `codegen` dependency groups in `task-sdk` and `airflow-ctl` pinned
   `datamodel-code-generator==0.41.0`. A number of published advisories affect
   releases in that range; the highest fix floor among them is 0.64.0, so this
   requires `>=0.71.0` to resolve clear of all of them with headroom rather than
   landing on the boundary release.
   
   Regenerating the models with the newer generator changes their shape: it no
   longer emits a spurious `= None` default for fields the OpenAPI spec lists as
   `required` but nullable. The regenerated models now match the spec instead of
   silently accepting payloads that omit those fields.
   
   **No Cadwyn migration is involved.** No datamodel, route, or spec file is
   touched — the server-side contract is byte-identical. This is purely a change
   in how the generator renders the same spec. The client pins
   `airflow-api-version`, so Cadwyn shapes every response to the version the
   client was generated against.
   
   Test fixtures that relied on the old leniency now pass those fields
   explicitly. Two of them were silently dropping a value by passing `schema_=`
   instead of the `schema` alias — the old implicit default masked the bug.
   
   The supervisor schema snapshot (`schema/schema.json`) is regenerated as a
   consequence, since the comms models inherit from the generated datamodels.
   
   Supersedes the `datamodel-code-generator` half of #70660, which bumps the 
same
   pin but does not regenerate the models and so does not carry the fixture
   updates that change requires.
   
   ---
   
   ##### 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]

Reply via email to