The GitHub Actions job "pip in /providers/informatica/dev/informatica_simulator 
for datamodel-code-generator - Update #1494687954" on airflow.git/main has 
failed.
Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]).

Head commit for run:
b3014293344d7e0fdce8bc62e9b6bb97c39baca2 / Jarek Potiuk <[email protected]>
Raise the datamodel-code-generator floor for the codegen toolchain (#70670)

* Raise the datamodel-code-generator floor for the codegen toolchain

The codegen dependency groups 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 require >=0.71.0 to resolve clear of
all of them with headroom rather than landing on the boundary release.

The newer generator no longer emits a spurious "= None" default for
fields the OpenAPI spec lists as required but nullable, so the
regenerated models now match the spec instead of silently accepting
payloads that omit those fields. This is a client-side rendering change
only -- no schema, route, or API version is touched, so no Cadwyn
migration is involved. Test fixtures that relied on the old leniency now
pass those fields explicitly; two of them were silently dropping a value
by passing "schema_=" rather than the "schema" alias.

* Carry the regenerated model shape into the remaining call sites

The regenerated models drop the implicit `= None` for spec-required nullable
fields, so every construction has to name them. Three test call sites and the
TypeScript SDK's generated types were still relying on the old leniency.

The fernet-key rotation test is a third instance of the `schema_=` mistake the
generator's leniency used to hide: the value was being dropped, not passed.

`ts-sdk/src/generated/supervisor.ts` derives from the same supervisor schema
snapshot, so it moves with it.

Report URL: https://github.com/apache/airflow/actions/runs/30519883039

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to