$ the-wire · showcase
Lazy reprs in nested union serialization, and a dependency train
By RepoJournal · Filed · About FastAPI & Pydantic · Composed from the cited sources · methodology
Pydantic merged a serialization fix that stops nested union serialization from eagerly formatting values, while FastAPI's day was entirely dependency bumps and release-note plumbing.
Lazily call repr of values during nested union serialization pydantic/pydantic
Nested union serialization now calls the repr of values lazily rather than up front, fixing the behavior reported in pydantic issue 14073. Serialization paths that build error or debug output from union members no longer pay the repr cost unless the repr is actually needed.
Publish `pydantic-core` wheels for PyPy 8.0 (`pp80` ABI) pydantic/pydantic
pydantic-core wheels will be published for PyPy 8.0 under the pp80 ABI, closing issue 13977. Code that pins or builds pydantic-core on PyPy would stop falling back to source builds, once those wheels ship.
⬆ Bump black from 26.5.1 to 26.10.1 fastapi/fastapi
Black moves from 26.5.1 to 26.10.1 in FastAPI's toolchain; the 26.10.1 release notes say it "fixes a security issue in Black's bundled GitHub Action" and encourage action users to update immediately. This is a dev-tooling bump in FastAPI's repo, not a change to any FastAPI release artifact.
⬆ Bump opentelemetry-api from 1.44.0 to 1.45.1 fastapi/fastapi
opentelemetry-api goes from 1.44.0 to 1.45.1, where the patch follows 1.45.0 with a fix in opentelemetry-api itself, described as making a type change around AnyValue. Nothing in the FastAPI API surface moves with it.
Correct naming collision examples in models and validation errors docs (#14077) pydantic/pydantic
The long tail is documentation and CI housekeeping: corrected naming-collision examples in the models and validation errors docs, refreshed contributing guidelines, and fixed uv cache keys for pydantic-core, plus gitpython moving from 3.1.62 to 3.2.1 in FastAPI's dependencies.