Pydantic Migration Guides
Fix validate_arguments migrations and keep the rewrite narrow enough to stay deterministic.
Start here
The direct decorator rename is validate_call. Stop when the decorator is wrapped or aliased.
Stop before automation when: Aliased decorator imports. Decorator wrappers.
from pydantic import validate_call
@validate_call
def create_user(email: str, age: int) -> None:
...
Repo fit check
Run the matching scanner locally first. Read the free findings and manual alternatives; consider paid cleanup only if supported patterns repeat enough to justify the price.
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewableWhy this page exists
This is a clean decorator migration when the import path is direct and the decorator is bare.
Direct answer
The direct decorator rename is validate_call. Stop when the decorator is wrapped or aliased.
Example
from pydantic import validate_arguments
@validate_arguments
def create_user(email: str, age: int) -> None:
...
from pydantic import validate_call
@validate_call
def create_user(email: str, age: int) -> None:
...
Decision path
The cleanup pack is strongest when the repo still uses direct pydantic imports and a clean validator/settings/config subset.
Before checkout
Price: $249.99 per team.
Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.
FAQ
The direct decorator rename is validate_call. Stop when the decorator is wrapped or aliased.
Automate only the supported subset: Direct validate_arguments to validate_call rewrites. Reporting for exactly where the decorator still appears. Links to the other direct-import Pydantic pages. Keep these cases in manual review: Aliased decorator imports. Decorator wrappers. Files bundled with unsupported validator signatures.
Use Pydantic v1 to v2 Migration Cleanup Pack only when this pattern repeats across enough files that manual cleanup is still costly. Use the free report and upstream guide to evaluate fit. Buy only if repeated supported edits justify the price; no paid assessment is required.
Purchase fit
One matching page is not enough by itself. Run the local scan, then buy only when the same supported pattern appears often enough to matter.
Replace @validator with @field_validator, Move BaseSettings to pydantic-settings, Convert Config to model_config, Replace @root_validator(pre=True) with @model_validator(mode="before"), Why post root validators need manual review, Move pydantic.v1 imports onto pydantic, Why Config.fields is a manual-review case, Why @validator(each_item=True) needs manual review