# Laravel 12 -> 13
**PHP floor: 8.3** (up from 8.2). Released March 17, 2026. Supports PHP 8.3, 8.4, 8.5.
The PHP bump IS the upgrade here. Laravel 13, like 12, was built to minimize breaking changes, the framework-level churn is small. The gate is the runtime.
## The one gate that matters
- **PHP 8.3 minimum, PHP 8.2 is dropped.** If your servers run 8.2, you cannot run Laravel 13 at all. Do the PHP upgrade as its own deploy first: move to 8.3 under Laravel 12, confirm the whole app and suite are green on 8.3, then upgrade the framework. Most "Laravel 13 broke my app" reports are really "PHP 8.2 -> 8.3 broke my app", deprecations, stricter type coercion, a package that was not 8.3-ready. Separating the two deploys is what makes the failure attributable.
## What is new (mostly non-breaking, adopt later)
- **PHP 8 attributes as an alternative to class properties** for configuring components, additive, your existing property-based config keeps working.
- **First-party AI SDK.**
- **`Cache::touch()`** for extending a cached item's TTL without rewriting it.
- **Reverb database driver** and **Passkeys** support.
None of these are required by the upgrade. Do the version bump clean, adopt features in later, separate commits.
## Checklist
- [ ] PHP 8.3 deployed under Laravel 12 first, app + suite green on 8.3
- [ ] Every dependency confirmed 8.3-compatible (`composer update` on 8.3 before touching the framework)
- [ ] Then bump `laravel/framework` to 13
- [ ] Suite green on staging, real flows exercised
- [ ] New features (AI SDK, attributes, passkeys) deferred to separate later commits
Official rename list: `laravel.com/docs/13.x/upgrade`.