Remove deprecated 422 status alias - #44
Merged
Merged
Conversation
chriswu727
marked this pull request as ready for review
July 16, 2026 03:30
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
1 participant
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.
What changed
Replace Starlette's deprecated
HTTP_422_UNPROCESSABLE_ENTITYalias withHTTP_422_UNPROCESSABLE_CONTENTin the validation error response.Why
The full API suite exposed seven deprecation warnings on validation-error paths. The
response code and API behavior stay exactly the same, but the supported status constant
keeps the suite warning-free and avoids a future Starlette removal.
Validation
make check