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

Weekly status: tiangolo/fastapi

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.

102 commits to master by 7 people, 62 pull requests merged, 69 open pull requests, 1 open issues on this page of results.

Stalled pull requests

Open, and untouched for seven days or more:

• #11782 📝 Add documentation on how to use the Django ORM inside FastAPI - last touched 363 days ago
• #14089 ✨ Improve JSON Parsing Error Messages - last touched 258 days ago
• #14952 Add regression test for Annotated + ForwardRef OpenAPI ( #13056 ) - last touched 242 days ago
• #14883 🐛 Fix implicit path params with converters - last touched 241 days ago
• #14115 📝 Fix CORS tutorial inconsistency with allow_credentials=True and wildcard values in `al - last touched 230 days ago

Issues nobody has picked up

None on this page of results.

---

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

If you maintain tiangolo/fastapi 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.