Bump fastapi to v0.125.0#2060
Merged
Merged
Conversation
✅ Deploy Preview for transformerlab canceled.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
deep1401
approved these changes
May 14, 2026
deep1401
left a comment
Member
There was a problem hiding this comment.
I'm able to start up the API and do the basic ops.
I will approve and merge right now. We'll deal with any issues in the future. I'll close the dependabot PR: #2080 and then see what dependabot has to say about the versions other than fastapi and deal with it separately
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Setting to draft until I finish a more thorough test.
This bumps FastAPI to a newer version with the primary benefit being that is resolves two vulnerabilities in starlette.
NOTE: starlette 0.46 → 0.50 is a meaningful jump. Middleware ordering, lifespan handlers, and exception handling have all seen small changes across those releases that the unit tests don't necessarily exercise. Hence the desire to run a more thorough test pass.