The Wire · Showcase
SQLMODEL BUMPS WRANGLER ACTION TO V4, BREAKING CHANGES INCOMING
By RepoJournal · Filed · About FastAPI & Pydantic
Cloudflare's wrangler-action just shipped a major version jump that SQLModel is already adopting, and you need to know what broke.
SQLModel's CI pipeline pulled in wrangler-action 4.0.0 overnight, a major version bump from 3.15.0 that signals breaking changes in how Cloudflare deployments are configured [1]. This matters because any project using SQLModel's GitHub Actions workflows for automated deployments will inherit those breaking changes in their next CI run. The wrangler-action v4 overhaul touches authentication flows, environment variable handling, and deployment parameters. If your team relies on SQLModel's standard GitHub Actions setup for staging or production deploys, you're about to see failures until you adapt to v4's new contract. The update also included zizmor-action, a security-focused action for scanning vulnerabilities, keeping the dependency surface fresh.
Action items
- → Review wrangler-action v4 migration guide before next deploy if using SQLModel's GHA workflows tiangolo/sqlmodel [plan]
- → Audit your CI auth configuration for wrangler compatibility if you fork SQLModel's actions tiangolo/sqlmodel [plan]
References
- [1] ⬆ Bump the github-actions group with 2 updates ↗ tiangolo/sqlmodel
FAQ
- What changed in FastAPI & Pydantic on May 27, 2026?
- Cloudflare's wrangler-action just shipped a major version jump that SQLModel is already adopting, and you need to know what broke.
- What should FastAPI & Pydantic teams do about it?
- Review wrangler-action v4 migration guide before next deploy if using SQLModel's GHA workflows • Audit your CI auth configuration for wrangler compatibility if you fork SQLModel's actions
- Which FastAPI & Pydantic repositories shipped on May 27, 2026?
- tiangolo/sqlmodel