The Wire · Showcase
BOTH FASTAPI AND SQLMODEL STRIP ZENSICAL CACHE FROM DOCS BUILDS
By RepoJournal · Filed · About FastAPI & Pydantic
FastAPI and SQLModel both disabled caching in their documentation workflows after discovering that Zensical's cache invalidation misses source and data changes, risking stale content in production builds.
The pattern mirrors a real problem: restoring cached artifacts when your inputs change unpredictably is a silent failure mode. FastAPI moved first [1], removing the useless `.cache` save from `build-docs.yml` after investigation revealed that the cache gets deleted before each Zensical build anyway, making the entire save step dead code. SQLModel followed with the same fix [2], noting that Zensical's invalidation logic doesn't account for all documentation sources or YAML data changes [3]. Both teams updated their release notes [4] [5]. This is infrastructure hygiene, not a user-facing change, but it's the kind of quiet reliability work that keeps docs pipelines from degrading silently over time.
One email a day. Unsubscribe in one click.
Keep up with FastAPI & Pydantic in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review your own doc build caching strategy if using Zensical fastapi/fastapi [plan]
- → Pull these fixes into any internal forks of FastAPI or SQLModel tiangolo/sqlmodel [plan]
References
- [1] 👷 Disable saving Zensical's `.cache` in `build-docs.yml` ↗ fastapi/fastapi
- [2] 👷 Remove Zensical docs cache (#2065) tiangolo/sqlmodel
- [3] 👷 Remove Zensical docs cache ↗ tiangolo/sqlmodel
- [4] 📝 Update release notes fastapi/fastapi
- [5] 📝 Update release notes tiangolo/sqlmodel