Uh oh!
There was an error while loading. Please reload this page.
Use HTTP_422_UNPROCESSABLE_CONTENT instead of HTTP_422_UNPROCESSABLE_ENTITY - #58828
Conversation
ashb
commented
Nov 28, 2025
Looks like we'll need some level of compat here. |
48ac8d9 to
e365c23CompareUh oh!
There was an error while loading. Please reload this page.
pierrejeambrun
left a comment
There was a problem hiding this comment.
LGTM, just one nit, non blocking
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
HTTP_422_UNPROCESSABLE_ENTITYis deprecated andHTTP_422_UNPROCESSABLE_CONTENTshould be used instead. That removes quite a few deprecation warnings when the api server starts^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.