Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Project Banner

Laravel Versions

A canonical source of everything you need to know about Laravel versions' support history and future.


Full list of all released versions here:


Test individual versions like this:

If you pass a major version (e.g. /8) you'll only see information about that major version, just like its entry in the full list (as seen above).

If you request a minor/patch version (e.g. /8.1 or /8.1.0) you'll see an additional section called specific_version that give you details about whether your provided release is the most up-to-date for its major. For example, this would be the output of requesting /8.1.5 at a time when 8.24.0 was the most up-to-date release for Laravel 8:

    "data": {
        "major": 8,
        "latest_minor": 24,
        "latest_patch": 0,
        "latest": "8.24.0",
        "is_lts": false,
        "released_at": "2020-09-08T00:00:00.000000Z",
        "ends_bugfixes_at": "2021-04-21T00:00:00.000000Z",
        "ends_securityfixes_at": "2021-09-08T00:00:00.000000Z",
        "status": "active",
        "specific_version": {
            "provided": "8.1.5",
            "needs_patch": true,
            "needs_major_upgrade": false
        "links": [
                "type": "GET",
                "rel": "major",
                "href": ""
                "type": "GET",
                "rel": "self",
                "href": ""
                "type": "GET",
                "rel": "latest",
                "href": ""

Potential statuses:

  • "active": receiving bug and security fixes
  • "security": only receiving security fixes
  • "end-of-life": no longer receiving security or bug fixes

Instructions for hosting/installing yourself



  1. (Optionally) Fork this repository

  2. Clone the repository locally

  3. Install dependencies with composer install

  4. Copy .env.example to .env and modify its contents to reflect your local environment.

  5. Generate an application key

    php artisan key:generate
  6. Create a database and point the DB_DATABASE to it in the .env file.

  7. Run database migrations. If you want to include seed data, add a --seed flag.

    php artisan migrate
  8. Install frontend dependencies with npm install

  9. Build frontend assets with npm run dev

  10. Configure a web server, such as the built-in PHP web server, to use the public directory as the document root.

    php -S localhost:8080 -t public
  11. Run tests with php artisan test.

Note: In order to make page caching work, you'll need to follow the installation instructions if you're installing this site on a production server.

How do I add additional languages to Laravel Versions?

  • fork this repository
  • copy this file of the English version with your translation: from lang/en.json file to lang/{code-lang}.json file (where 'code-lang' is the short code of the translated language)
  • add language in the configuration file config/localized-routes.php
    • in the variable supported-locales, the code of the supported language
    • in the variable locales-name-native the language code as the key, and the value of the name of the native language, which will be displayed in the menu.
  • add a pull request with the name of the language
    • ex: [pl] New language


No description, website, or topics provided.


Security policy





No releases published


No packages published