Laravel Release Cycle: Versions &amp; Support Policy | Mohamed Said       [Skip to content](#main)  [ ![](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed SaidLaravel Backend Engineer ](https://www.msaied.com/public) - [Home](https://www.msaied.com/public)
- [Projects](https://www.msaied.com/public/projects)
- [Articles](https://www.msaied.com/public/articles)
- [Certificates](https://www.msaied.com/public/certificates)
- [About](https://www.msaied.com/public#about)

           [  Contact](https://www.msaied.com/public#contact) Menu 

Menu
----

Close 

 - [HomeStart here](https://www.msaied.com/public)
- [ProjectsCase studies](https://www.msaied.com/public/projects)
- [ArticlesEngineering notes](https://www.msaied.com/public/articles)
- [CertificatesCredentials](https://www.msaied.com/public/certificates)
- [AboutHow I work](https://www.msaied.com/public#about)
- [ContactGet in touch](https://www.msaied.com/public#contact)

  [Start a conversation](https://www.msaied.com/public#contact) [WhatsApp](https://wa.me/201094619204) [Email](mailto:hello@msaied.com) 

 1. [Home](https://www.msaied.com/public)
2. /
3. [Articles](https://www.msaied.com/public/articles)
4. /
5. [Laravel](https://www.msaied.com/public/articles?category=laravel)
6. /
7. Laravel Release Cycle: Versions, Support Policy, and Dates

   [Laravel](https://www.msaied.com/public/articles?category=laravel) 

 Laravel Release Cycle: Versions, Support Policy, and Dates
===========================================================

 Laravel ships one major version per year in Q1, with weekly minor and patch releases in between. Here is everything you need to know about the release cycle, support windows, and upgrade strategy.

 ![](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) [Mohamed Said](https://www.msaied.com/public#person) Published 29 Sep 2026 · Updated 29 Sep 2026 · 4 min read

ShareCopy linkCopied

 ![Laravel Release Cycle: Versions, Support Policy, and Dates](https://cdn.msaied.com/718/05d0e66985cc7bda5c0be6c37bb8da65.png) 

  On this page +1. [Semantic Versioning](#semantic-versioning)
2. [Weekly Minor and Patch Releases](#weekly-minor-and-patch-releases)
3. [Annual Major Releases](#annual-major-releases)
4. [Support Policy](#support-policy)
5. [Composer Version Constraints](#composer-version-constraints)
6. [Upgrading to a New Major Version](#upgrading-to-a-new-major-version)
7. [Where Development Happens](#where-development-happens)
8. [Key Takeaways](#key-takeaways)

 Laravel ships one major version a year, typically in Q1, and tags minor and patch releases on most weeks throughout the year. Understanding the release cycle helps you plan upgrades, set the right Composer constraints, and avoid running an unsupported version in production.

Semantic Versioning
-------------------

Laravel follows [Semantic Versioning](https://semver.org/) since Laravel 6 (September 2019). A version number like `13.33.0` breaks down as:

- **MAJOR** (`13`) — breaking changes
- **MINOR** (`33`) — new features, backward-compatible
- **PATCH** (`0`) — bug fixes only, backward-compatible

Before Laravel 6, the second number signaled major releases (e.g., 5.4 → 5.5 could break your app). That is no longer the case.

Weekly Minor and Patch Releases
-------------------------------

The Laravel team tags a release most Tuesdays. A minor number in the thirties does not mean you are behind — it just means a busy year of features. Moving from `13.1` to `13.33` is a single `composer update` because minor and patch releases never contain breaking changes.

Annual Major Releases
---------------------

Laravel moved from a six-month to a yearly major release cycle in January 2021. Major versions have landed as follows:

| Version | Release Date | |---|---| | Laravel 9 | February 8, 2022 | | Laravel 10 | February 14, 2023 | | Laravel 11 | March 12, 2024 | | Laravel 12 | February 24, 2025 | | Laravel 13 | March 17, 2026 | | Laravel 14 | Q1 2027 (expected) |

Because most features ship in weekly minor releases, a major version primarily holds back only breaking changes. Raising the minimum PHP version is the most common one — Laravel 13 requires PHP 8.3, and Laravel 14 will require PHP 8.4.

Support Policy
--------------

Every major Laravel release receives **bug fixes for 18 months** and **security fixes for 2 years**. There are no LTS releases anymore; Laravel 6 was the last one.

| Version | Bug Fixes Until | Security Fixes Until | |---|---|---| | 14 (expected) | Q3 2028 | Q1 2029 | | 13 | Q3 2027 | March 17, 2028 | | 12 | August 13, 2026 | February 24, 2027 | | 11 | September 3, 2025 | March 12, 2026 | | 10 | August 6, 2024 | February 4, 2025 |

As of late 2026, Laravel 10 and 11 are end of life. Laravel 12 receives security fixes only. **Laravel 13 is the only version still receiving bug fixes.**

Plan major upgrades around the 18-month bug fix window, not the two-year security window. Laravel 12 bug fixes ended on August 13, 2026 — less than five months after Laravel 13 shipped.

Composer Version Constraints
----------------------------

Use a caret constraint in `composer.json` to accept all `13.x` releases while blocking `14.0`:

```json
"require": {
    "laravel/framework": "^13.0"
}

```

Weekly minor releases arrive automatically via `composer update`. The major upgrade waits until you manually bump the constraint.

> **Note:** Named arguments are not covered by Laravel's backward compatibility promise. The team may rename method parameters in a minor release, so avoid calls like `Cache::put(key: 'foo', value: 'bar')`.

Upgrading to a New Major Version
--------------------------------

The team targets upgrades that take one day or less. Each major version ships with a detailed upgrade guide that rates the likelihood of each breaking change affecting your application. [Laravel Shift](https://laravelshift.com/) automates the process and opens a pull request with a commit per change, and it now uses AI to handle even more of the upgrade automatically.

Where Development Happens
-------------------------

The `laravel/framework` repository maintains a branch per major version (`11.x`, `12.x`, `13.x`) and a `master` branch for the next major release:

- Bug fixes → latest bug-fix branch (`13.x`)
- Backward-compatible features → `13.x`, ships in the next weekly release
- Breaking changes → `master` (becomes Laravel 14)

Key Takeaways
-------------

- Laravel ships one major version per year (~Q1), with weekly minor/patch releases in between.
- Every major version gets 18 months of bug fixes and 2 years of security fixes — no LTS.
- Laravel 13 (PHP 8.3+, released March 17, 2026) is the only version currently receiving bug fixes.
- Laravel 14 is expected in Q1 2027 and will require PHP 8.4.
- Use `^13.0` in `composer.json`; avoid named arguments for framework methods.
- Plan upgrades around the 18-month bug fix window, not the 2-year security window.

---

*Source: [Laravel Release Cycle: Versions, Support Policy, and Dates — Laravel News](https://laravel-news.com/laravel-releases)*

- [Laravel](https://www.msaied.com/public/articles?search=Laravel)
- [Release Cycle](https://www.msaied.com/public/articles?search=Release%20Cycle)
- [Support Policy](https://www.msaied.com/public/articles?search=Support%20Policy)
- [Versioning](https://www.msaied.com/public/articles?search=Versioning)
- [Upgrade Guide](https://www.msaied.com/public/articles?search=Upgrade%20Guide)

 Frequently asked questions 
---------------------------

  How long does Laravel support each major version?Each major Laravel release receives bug fixes for 18 months and security fixes for 2 years from its release date. There are no LTS releases since Laravel 6.

   Is it safe to run composer update on a Laravel 13 project?Yes. Minor and patch releases never contain breaking changes, so updating from any 13.x version to the latest 13.x is safe. The caret constraint `^13.0` in composer.json ensures you stay on the 13.x line and do not accidentally pull in Laravel 14.

   When should I upgrade from Laravel 12 to Laravel 13?Laravel 12 bug fixes ended on August 13, 2026 — roughly five months after Laravel 13 shipped. You should upgrade before that date to keep receiving bug fixes, rather than waiting until the security fix window closes in February 2027.

   ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp)About the author
----------------

[Mohamed Said](https://www.msaied.com/public#person)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow.

[About](https://www.msaied.com/public#about) [GitHub ↗](https://github.com/EG-Mohamed) [LinkedIn ↗](https://www.linkedin.com/in/msaiedm/) [WhatsApp ↗](https://wa.me/201094619204) [Email Address ↗](mailto:hello@msaied.com) [My CV ↗](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)  

   [Previous articleLaravel Queues in Production: Dead-Letter Patterns, Retry Strategies, and Observability](https://www.msaied.com/public/articles/laravel-queues-in-production-dead-letter-patterns-retry-strategies-and-observability) [Next articleMailbox for Laravel: Preview and Test Rendered Email Without a Separate Mail Service](https://www.msaied.com/public/articles/mailbox-for-laravel-preview-and-test-rendered-email-without-a-separate-mail-service)  

   On this page
-------------

1. [Semantic Versioning](#semantic-versioning)
2. [Weekly Minor and Patch Releases](#weekly-minor-and-patch-releases)
3. [Annual Major Releases](#annual-major-releases)
4. [Support Policy](#support-policy)
5. [Composer Version Constraints](#composer-version-constraints)
6. [Upgrading to a New Major Version](#upgrading-to-a-new-major-version)
7. [Where Development Happens](#where-development-happens)
8. [Key Takeaways](#key-takeaways)

 ###  Have a technical challenge?

 Tell me what you’re building. I reply within two working days.

[Start a conversation](https://www.msaied.com/public#contact) 

   Related articles
-----------------

 [ ![](https://cdn.msaied.com/740/cce86edc21eddcbdd2f2454fadaf9c70.png)  · 3 min read### The Pipeline Pattern in Laravel: Custom Pipelines Beyond Middleware

5 Oct 2026 ](https://www.msaied.com/public/articles/the-pipeline-pattern-in-laravel-custom-pipelines-beyond-middleware-1) [ ![](https://cdn.msaied.com/739/2d6897fdcdcf090613f96f72a64b8a78.png)  · 4 min read### MySQL Full-Text Search in Laravel: Indexes, Relevance Scoring, and Boolean Mode

4 Oct 2026 ](https://www.msaied.com/public/articles/mysql-full-text-search-in-laravel-indexes-relevance-scoring-and-boolean-mode) [ ![](https://cdn.msaied.com/738/073696a3fefe18bec825beec5ac658f5.png)  · 4 min read### Laravel Queue Rate-Limited Middleware: Throttling Jobs Without Losing Work

4 Oct 2026 ](https://www.msaied.com/public/articles/laravel-queue-rate-limited-middleware-throttling-jobs-without-losing-work) 

  Have a technical challenge?
----------------------------

Tell me what you’re building. I reply within two working days.

 [Discuss your project ↗](https://www.msaied.com/public#contact) 

  © 2026 Mohamed Said · Built with Laravel, meant to last.Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow.

 - [Home](https://www.msaied.com/public)
- [Articles](https://www.msaied.com/public/articles)
- [Certificates](https://www.msaied.com/public/certificates)
- [GitHub](https://github.com/EG-Mohamed)
- [LinkedIn](https://www.linkedin.com/in/msaiedm/)
- [WhatsApp](https://wa.me/201094619204)
- [Email Address](mailto:hello@msaied.com)
- [My CV](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)
- [Sitemap](https://www.msaied.com/public/sitemap.xml)
