Blogs

Home » Laravel 12 Released with New Features & Long-Term Support

Laravel 12 Released with New Features & Long-Term Support

Release & Approach

Laravel 12 was officially released on February 24, 2025.
This release emphasizes minimal breaking changes and focuses on maintenance, dependency updates, and developer experience enhancements.
According to the release notes from Laravel, Laravel 12 offers new starter kits for React, Vue, and Livewire, leveraging the latest frontend stack technologies (Inertia 2, TypeScript, shadcn/ui).

Major Features & Improvements in Laravel 12

Here’s a breakdown of the most notable features and changes in Laravel 12:

Feature / Change	Description & Impact	Upgrade Considerations
New Starter Kits	Out-of-the-box starter scaffolding for React, Vue, and Livewire, including authentication, UI components, and integration with modern tooling.	You can use them in new projects, or migrate certain components of your frontend stacks. However, they might not completely replace heavily customized systems right away.
PHP Version Requirement & Compatibility	Laravel 12 requires PHP 8.2+.	If your application is on older PHP versions, you must upgrade PHP first.
Concurrency & Result Mapping	The `Concurrency::run()` method now returns results keyed by the original array keys, improving clarity when using async concurrent tasks.	Minor adjustments may be needed in areas where you consumed the results as numeric arrays.
Container Class Dependency Resolution	The service container now respects default values for class properties when resolving instances, giving more predictable behavior.	If your code relied on fallback behaviour (resolving without defaults), review impacted classes.
Local Filesystem Default Path Changed	If `local` disk isn’t explicitly configured, its root path now defaults to `storage/app/private` (instead of `storage/app`).	Explicitly define your `local` disk path if you want legacy behavior.
Validation Rule: SVGs excluded by default	The `image` validation rule by default excludes SVG files. To allow SVGs, you must explicitly allow them: `image:allow_svg` or via `File::image(allowSvg: true)`.	If your app accepted SVG uploads before, you’ll need to adjust your validation rules.
Native Health Checks	Laravel 12 adds built-in health check routes to monitor application status (e.g. DB, cache, queues) without third-party packages.	Useful for deployment/monitoring setups (Kubernetes, Docker) you can customize which checks to expose.
Route Attributes (PHP 8+ attribute routing)	You can now define routes by annotating controller methods using PHP attributes instead of relying purely on route files.	This is optional and additive route files still function, but attribute routing helps keep everything more concise.
Improved Job Batching & Lifecycle Events	More robust job batching with lifecycle callbacks, better monitoring and error-handling mechanisms in queued jobs.	For apps with heavy background processing, take advantage of new features to simplify logic.
Support & Maintenance Updates	Laravel 12 supports bug fixes until August 13, 2026, and security fixes until February 24, 2027.	Create an upgrade plan before the support period runs out.
Other Minor Enhancements & Breaking Behavior Adjustments	Nested array request merging tweaks in `mergeIfMissing()` Image validation excludes SVGs (see above) Improved defaults in container resolution Some shifts in config or naming tweaks Emphasis on performance, updated dependencies Other small bugfixes and deprecations	Review upgrade guide to spot all low-impact changes and adjust accordingly.

Support Policy & Lifecycle

According to community sources and versioning pages, Laravel 12 is supported for bug fixes until August 13, 2026, and security fixes until February 24, 2027.
Laravel has adopted a non-LTS, yearly major version cadence, where each release receives a defined support window (18 months bug fixes and 2 years security fixes) unless designated LTS.
Versioning site shows Laravel 12 supports PHP from 8.2 to 8.4.

Laravel 12 is not an LTS release in the usual sense (unless otherwise mentioned), but it does have a reasonable support cycle. The application needs to be ready for an upgrade before support ends.

Upgrade Path & Migration Strategies

Upgrade Guide Highlights (from official docs)

Some of the key changes worth checking when migrating:

Concurrency result index mapping changed.
Container class dependency resolution behavior changed in default property handling.
If your application used image validation assuming SVG support, you must explicitly allow SVGs.
Local filesystem root path change for local disk default.
Some method behavior changes like mergeIfMissing() in handling nested dot-notation keys.

It’s advisable to run automated tests, check deprecations, and review upgrade diff comparisons in laravel/laravel repository.

Steps to Upgrade Safely

Ensure your app is running on PHP 8.2+ and all dependencies support 12.
Update composer.json to "laravel/framework": "^12.0" and run composer update.
Review the upgrade guide in Laravel’s documentation to catch all breaking or changed behaviors.
Run your test suite and fix failing tests.
Check configurations and environment variables line by line (some defaults may shift).
Deploy to staging, monitor logs and runtime behavior.
Use new features gradually; starter kits only for new modules or incremental adoption.

Why Start New Projects on Laravel 12?

You’ll get latest tooling, security, and developer experience improvements out of the box.
Starter kits reduce boilerplate to get frontend + backend working rapidly.
You remain within the support window and avoid having to upgrade soon again.
Future dependencies and ecosystem packages will prioritize compatibility with latest major versions.