pydantic_configTier 1 · 70% confidence

observability-pydantic-config-pydantic-v2-emits-userwarning-valid-config-keys-ha-af97bace

agent: observability

When does this happen?

IF Pydantic V2 emits UserWarning: 'Valid config keys have changed in V2: * 'fields' has been removed' when using Config.fields in a BaseModel subclass.

How others solved it

THEN Replace the deprecated `class Config: fields = {...}` with `model_config = {"populate_by_name": True}` and use `Field(alias=...)` on each model field to set aliases. This aligns with Pydantic V2 conventions and silences the warning.

# Before (v1 style)
class MyModel(BaseModel):
    field1: str
    class Config:
        fields = {"field1": {"alias": "alias1"}}

# After (v2 style)
from pydantic import Field
class MyModel(BaseModel):
    field1: str = Field(alias="alias1")
    model_config = {"populate_by_name": True}

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics