Repository navigation
Update dependency fastapi to ~=0.161.1 - #115
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
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
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.
This PR contains the following updates:
~=0.143.1→~=0.161.1Release Notes
fastapi/fastapi (fastapi)
v0.161.1Compare Source
Fixes
v0.161.0Compare Source
Features
v0.160.0Compare Source
Query, header, cookie, and form parameter models now apply their
extraconfiguration to all submitted fields in the same parameter location, consistent with Pydantic behavior. This includes fields declared in other models, individual parameters, or dependencies, which were previously excluded.With
extra="forbid", fields outside the model are rejected even if another parameter declares them. Withextra="allow", those fields are included as model extras. With the defaultextra="ignore", they are ignored.Breaking Changes
extraconfiguration to sibling fields. PR #16594 by @tiangolo.Internal
v0.159.1Compare Source
Features
v0.159.0Compare Source
Features
v0.158.2Compare Source
Features
v0.158.1Compare Source
Fixes
v0.158.0Compare Source
Features
v0.157.0Compare Source
Features
Docs
Internal
v0.156.8Compare Source
Fixes
bytes. PR #16566 by @tiangolo.v0.156.7Compare Source
Fixes
AliasChoices. PR #16564 by @tiangolo.v0.156.6Compare Source
Fixes
v0.156.5Compare Source
Fixes
AliasChoicesfor path parameters. PR #16560 by @tiangolo.v0.156.4Compare Source
Fixes
AliasChoicesfor named JSON body parameters. PR #16559 by @tiangolo.AliasChoicesextraction for form models. PR #16557 by @tiangolo.v0.156.3Compare Source
Fixes
AliasChoicesfor query parameters, headers, and cookies. PR #16555 by @tiangolo.v0.156.2Compare Source
Fixes
v0.156.1Compare Source
Fixes
v0.156.0Compare Source
Fixes
Field()attributes in request parameters. PR #16547 by @tiangolo.v0.155.0Compare Source
The deprecated
**extrakeyword arguments have been removed fromPath,Query,Header,Cookie,Body,Form, andFile. Unknown keyword arguments now raiseTypeError. For additional JSON Schema properties, replace, for example,Query(custom="value")withQuery(json_schema_extra={"custom": "value"}).Breaking Changes
**extrafrom request parameters. PR #16545 by @tiangolo.v0.154.0Compare Source
Features
v0.153.0Compare Source
Unions of form models now apply the same browser form handling as individual models. Empty scalar fields use defaults or produce missing-field errors, empty list items are preserved, omitted boolean fields become
False, and unselected files are treated as missing. JSON request bodies are unchanged.Fixes
v0.152.0Compare Source
Validation errors for header parameter models now report the HTTP header name, such as
int-val, instead of the Python field name,int_val. Explicit aliases,Header(convert_underscores=False), and Pydantic models withloc_by_alias=Falsekeep their existing behavior.Fixes
v0.151.0Compare Source
JSON request bodies now distinguish an explicit
nullfrom an omitted value. For individualBodyparameters,nullis validated asNone: nullable types accept it, and non-nullable types reject it even when a default is defined. Defaults and default factories apply only when the value is omitted. This applies both to parameters inside JSON objects and to parameters representing the entire body. Clients that usednullto request a default should omit the value instead.When a JSON object is expected because of
Body(embed=True)or multiple body parameters, sendingnullas the entire body now returns a validation error.Breaking Changes
v0.150.0Compare Source
When no file is selected, browsers submit a file part with an empty filename and empty content. FastAPI now treats this as missing: required file fields return a validation error, and fields with defaults or default factories use them. Unselected inputs are ignored in lists of files. Named zero-byte files are still accepted.
Breaking Changes
v0.149.0Compare Source
Browsers submit empty text inputs as empty strings (
""). FastAPI now treats empty scalar form values as missing in form models, matching individualFormparameters. Required fields return a validation error. Fields with defaults or default factories use them and remain unset inmodel_dump(exclude_unset=True).Empty strings inside lists are preserved. Omitted boolean form fields still become
False. JSON requests and direct Pydantic validation are unchanged.Breaking Changes
v0.148.0Compare Source
Defaults for omitted
Query,Header,Cookie, andFormparameters and model fields are no longer treated as user input. Defaults are not validated unlessvalidate_default=Trueis enabled. If you rely on validators running for omitted values, enable default validation withField(validate_default=True)for model fields or, for example,Query(validate_default=True)for individual parameters.Body(validate_default=True)is now honored too.For parameter models, applying a default no longer marks a field as explicitly set, so
model_dump(exclude_unset=True)excludes it. Default factories run once, and validation errors no longer include injected defaults ininput.Omitted boolean form fields still become
Falseand count as explicitly set.Breaking Changes
v0.147.0Compare Source
Omitted
boolandbool | Noneform fields are now interpreted asFalse, matching unchecked HTML checkboxes. This applies to individualFormparameters and form models, including required fields and fields with defaults ofTrueorNone. The inferred value is considered explicitly set, including inmodel_dump(exclude_unset=True).JSON requests and direct Pydantic validation are unchanged. See Boolean Form Fields.
Breaking Changes
Internal
v0.146.0Compare Source
The
root_pathparameter inFastAPI()is deprecated. Configure the server withfastapi run --root-path /api/v1instead.Breaking Changes
root_pathparameter inFastAPI. PR #16520 by @tiangolo.v0.145.0Compare Source
Breaking Changes
openapi_prefixand unused**extrafromFastAPI. PR #16518 by @tiangolo.Docs
v0.144.0Compare Source
Features
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.