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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FastAPI upgrade enables strict Content-Type checking by default
Medium Severity
Bumping
fastapifrom 0.112.2 to 0.135.1 activates the strict Content-Type validation introduced in 0.132.0. AllFastAPI()instantiations in the codebase (infastapi_endpoint.pyandfastapi_endpoint_registry.py) lack thestrict_content_type=Falseparameter. POST/PUT/PATCH requests from API clients that omit a validContent-Type: application/jsonheader will now be rejected with 422 errors instead of being processed normally.