Upper-bind FastAPI until Cadwyn is adapted to FastAPI 0.126.0+ #59726
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Limited due to backwards incompatible (but deliberate) changes in FastAPI 0.126.0 which break Cadwyn way of copying classes and break serialization. As explained in fastapi/fastapi#14582 (comment), Cadwyn needs to adapt to those changes and we cannot move to newer version of FastAPI This is tracked in Cadwyn in zmievsa/cadwyn#314
jscheffl
approved these changes
Dec 22, 2025
sunank200
approved these changes
Dec 22, 2025
kaxil
approved these changes
Dec 22, 2025
johnslavik
reviewed
Dec 22, 2025
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 3bf0ed8 v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Dec 22, 2025
…26.0+ (apache#59726) Limited due to backwards incompatible (but deliberate) changes in FastAPI 0.126.0 which break Cadwyn way of copying classes and break serialization. As explained in fastapi/fastapi#14582 (comment), Cadwyn needs to adapt to those changes and we cannot move to newer version of FastAPI This is tracked in Cadwyn in zmievsa/cadwyn#314 (cherry picked from commit 3bf0ed8) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Member
Author
|
Backport in #59727 |
Member
Author
|
Ah no. FastAPI in 3.1* is limited to < 0.118.0 |
Subham-KRLX
pushed a commit
to Subham-KRLX/airflow
that referenced
this pull request
Jan 2, 2026
…e#59726) Limited due to backwards incompatible (but deliberate) changes in FastAPI 0.126.0 which break Cadwyn way of copying classes and break serialization. As explained in fastapi/fastapi#14582 (comment), Cadwyn needs to adapt to those changes and we cannot move to newer version of FastAPI This is tracked in Cadwyn in zmievsa/cadwyn#314
stegololz
pushed a commit
to stegololz/airflow
that referenced
this pull request
Jan 9, 2026
…e#59726) Limited due to backwards incompatible (but deliberate) changes in FastAPI 0.126.0 which break Cadwyn way of copying classes and break serialization. As explained in fastapi/fastapi#14582 (comment), Cadwyn needs to adapt to those changes and we cannot move to newer version of FastAPI This is tracked in Cadwyn in zmievsa/cadwyn#314
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Limited due to backwards incompatible (but deliberate) changes in FastAPI 0.126.0 which break Cadwyn way of copying classes and break serialization. As explained in
fastapi/fastapi#14582 (comment), Cadwyn needs to adapt to those changes and we cannot move to newer version of FastAPI This is tracked in Cadwyn in zmievsa/cadwyn#314
^ 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.