henry3260 opened a new pull request, #75639: URL: https://github.com/apache/airflow/pull/75639
## Why #75610 moved seven response-only models off `StrictBaseModel`, but left the class itself untouched. Its docstring says to use it for "models that should not have any extra fields in the payload", which reads as a general recommendation — and is how those seven came to pick it. Two reasons limit it to request bodies, and neither is recorded at the class: - A response model is instantiated from a source object that holds more than the model returns; selecting from that object is the model's job. `extra="forbid"` rejects the construction, which is what #44306 worked around when it split the two base classes. - `extra="forbid"` reaches the spec as `additionalProperties: false`, so a generated client such as airflowctl rejects a field that a newer server adds. That is the failure #75610 had to fix. ## What The docstring states the constraint and both reasons. No behaviour change, no other file touched. related: #75610 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (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]
