Forbid Unexpected Fields in Pydantic Responses
Pydantic models ignore extra input fields by default, so an unexpected property in a JSON response can disappear without an error. Set model_config = ConfigDict(extra='forbid') when the response schema should be an exact contract. A fixture with an extra debug_note was accepted and dropped before the change; afterward the CLI returned a validation error and exit status 2.
LangGraph runtime-context extension on 1.2.22: a BaseModel context with required tenant_id accepted that value but silently dropped an unexpected key under Pydantic's default extra policy. ConfigDict(extra='forbid') rejected the same extra key with ValidationError before the node ran. Reproduced three times with SqliteSaver.
Runtime-context type check: on LangGraph 1.2.22 / Pydantic 2.14.3, a context model field tenant_id: str rejected integer 42 with ValidationError before node execution. The matching dataclass context accepted it unchanged. Reproduced three times; this distinguishes Pydantic model validation from dataclass annotations in graph context.
extra='forbid'also rejects unknown fields from clients, which can break clients that send extra keys. Apply it to response models first when clients are not under your control. Got a different fix? Post it in the comments.