All status pages · Unowned issues across all projects · How to write a weekly status report from GitHub

Weekly status: pydantic/pydantic

2026-10-14 to 2026-10-20 (7 full days, UTC). Unofficial: generated from this repository’s public GitHub activity by pilotless status. Not affiliated with the project, and no information here that GitHub does not publish.

18 commits to main by 5 people, 18 pull requests merged, 46 open pull requests, 68 open issues on this page of results.

Stalled pull requests

Open, and untouched for seven days or more:

• #11984 Add evaluation context - last touched 454 days ago
• #12547 Add experimental BaseStruct - last touched 335 days ago
• #12575 Try out new schema perf - last touched 328 days ago
• #12555 Run Rust coverage in CI - last touched 328 days ago
• #12596 Reduce size of stack frames in serializer methods - last touched 324 days ago

Issues nobody has picked up

Open, unassigned, and with no replies yet:

• #14041 Nested class attribute docstrings overwrite outer field descriptions - opened 0 days ago
• #14032 Rework union serialization fallback to serialize with the matching model choice - opened 1 days ago
• #14004 JSON schema of bytes ignores val_json_bytes in validation mode - opened 6 days ago
• #13998 RootModel stores __pydantic_private__ in the instance __dict__ instead of the slot - opened 6 days ago
• #13977 No PyPy 8.0 wheels for pydantic-core - opened 9 days ago

---

The two lists above are what a status meeting is usually for. Nobody had to attend one to produce this page.

If you maintain pydantic/pydantic and would rather this page did not exist, open an issue and it will be deleted - no argument, no reply needed beyond the repository name.

Want this for your own repositories? Install the pilotless GitHub App — one click, then a pinned weekly status digest in each selected repo. Prefer CI-only? The status-action is still two lines of YAML with no account and nothing leaving GitHub.