$ the-wire · showcase
PYDANTIC TIGHTENS NAMED TUPLE VALIDATION, FASTAPI PULLS 12 DEPENDENCY UPDATES
By RepoJournal · Filed · About FastAPI & Pydantic · Composed from the cited sources · methodology
2 people shipped this
Pydantic ships a dedicated named-tuple core schema that fixes four critical validation edge cases, while FastAPI and SQLModel ride a wave of upstream bumps across the toolchain.
Pydantic merged a new named-tuple core schema [1] that replaces the incorrect 'call' validation pattern, fixing multiple reported issues where named tuples were validated using function-call semantics [1]. The same PR also raises explicit TypeErrors on invalid index_key serialization handlers [2], preventing silent failures that users may have cargo-culted from outdated docstring examples. On the dependency front, FastAPI pulled 12 package updates including httpx2 from 2.5.0 to 2.9.1, mypy from 2.1.0 to 2.3.0, and strawberry-graphql up three minor versions [3]. SQLModel followed suit with 7 updates of its own, bumping FastAPI itself to 0.140.0, Typer to 0.27.0, and ruff across both repos [4]. These are routine maintenance cycles, but the Pydantic schema work addresses real production pain points that have accumulated in the issue tracker.
Action items
- → Review Pydantic PR #13505 if you validate named tuples - schema behavior is changing pydantic/pydantic [plan]
- → Merge FastAPI and SQLModel dependency updates in your next maintenance window fastapi/fastapi [monitor]
- → Test your serialization handlers if using index_key - PR #13506 now raises on invalid signatures pydantic/pydantic [plan]
References
- [1] Add a `named-tuple` core schema ↗ pydantic/pydantic
- [2] Raise explicit `TypeError` on invalid `index_key` serialization wrap handler ↗ pydantic/pydantic
- [3] ⬆ Bump the python-packages group with 12 updates ↗ fastapi/fastapi
- [4] ⬆ Bump the python-packages group with 7 updates ↗ tiangolo/sqlmodel
