The Wire · Showcase
CI CACHE GOES DARK ACROSS FASTAPI AND SQLMODEL
By RepoJournal · Filed · About FastAPI & Pydantic
A routine bump to setup-uv just disabled CI caching by default for three event types in both FastAPI and SQLModel.
YuriiMotov bumped `setup-uv` to `10.0.1` across both fastapi/fastapi [1] and tiangolo/sqlmodel [2], inheriting a security-driven breaking change from v10.0.0 that disables caching for workflows triggered by `workflow_run`, `pull_request_target`, and `release`. The release notes say v10.0.0 "disables cache by default" [1], so if your CI depends on those triggers, expect slower jobs until you opt back in. The teams are intentionally keeping the new behavior for now. Meanwhile, pydantic cleaned up its agent skill docs [3] and clarified the note about plain model serializers returning a non-dict [4], closing issue #13701. Nothing else moved across the stack, so the real signal is the CI cache shift: verify your FastAPI and SQLModel pipelines before your next release-triggered build.
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
- → Check your CI workflows for workflow_run, pull_request_target, or release triggers and re-enable cache if needed after the setup-uv 10.0.1 bump fastapi/fastapi [immediate]
- → Check the same setup-uv bump impact on SQLModel CI pipelines tiangolo/sqlmodel [immediate]
- → Review the clarified serializer note in pydantic docs to avoid non-dict return surprises pydantic/pydantic [monitor]
References
- [1] ⬆️ Bump `setup-uv` action to `10.0.1` ↗ fastapi/fastapi
- [2] ⬆️ Bump `setup-uv` action to `10.0.1` ↗ tiangolo/sqlmodel
- [3] Fix typos, phrasing, and missing imports in SKILL.md ↗ pydantic/pydantic
- [4] Clarify note about plain model serializers returning a non-dict ↗ pydantic/pydantic