Laravel 13.x Shift

[ohnotnow]

This pull request includes the changes for upgrading to Laravel 13.x. Feel free to commit any additional changes to the shift-175863 branch.

Before merging, you need to:

• Checkout the shift-175863 branch
• Review all pull request comments for additional changes
• Run composer update (if the scripts fail, try with --no-scripts)
• Clear any config, route, or view cache
• Thoroughly test your application (no tests?, no CI?)

If you get stuck, never hesitate to email support. If you need more help with your upgrade, check out the Human Shifts.

[ohnotnow]

⚠️ Shift upgraded your configuration files by defaulting them and merging your true customizations. These include values which are not changeable through core ENV variables.

You should review this commit for additional customizations or opportunities to use new ENV variables. If you have a lot of customizations, you may undo this commit with git revert 74397b50 and make the config file changes manually.

[ohnotnow]

⚠️ The default values for CACHE_PREFIX, REDIS_PREFIX, and SESSION_COOKIE changed in Laravel 13. If you are not setting these values explicitly, this change could cause cache or session invalidation after upgrading. As these defaults have changed a few times in recent Laravel versions, Shift recommends explicitly setting these ENV variables in your environment to ensure consistent behavior when upgrading.

 ✨ Automate more with AI...

Shift automates the changes it determines are reliable. If you want to push this automation further, you may paste the following prompt into your AI of choice:

I'm upgrading to Laravel 13. The default values for `CACHE_PREFIX`,
`REDIS_PREFIX`, and `SESSION_COOKIE` have changed. In Laravel 12 and earlier,
these were derived from `APP_NAME` using `Str::slug(env('APP_NAME', 'laravel'),
'_')` as a base (e.g. `myapp_cache_`, `myapp_database_`, `myapp_session`).
Please check my config files and `.env` to determine if these are explicitly set
or relying on the old defaults. If relying on defaults, suggest the explicit
values I should add to my `.env` to preserve the previous behavior.

[ohnotnow]

⚠️ The default cache configuration now includes a serializable_classes option set to false. This hardens cache unserialization behavior to help prevent PHP deserialization attacks. If your application stores PHP objects in cache, you should update this value to an array of the classes that may be unserialized.

 ✨ Automate more with AI...

Shift automates the changes it determines are reliable. If you want to push this automation further, you may paste the following prompt into your AI of choice:

I'm upgrading to Laravel 13. The default cache configuration now includes a
`serializable_classes` option set to `false` to prevent PHP deserialization
attacks. Please search my codebase for any code that stores PHP objects in the
cache (e.g. using `Cache::put()`, `cache()`, or `remember()` with object
values). If found, identify the classes being cached and suggest the explicit
list of classes I should set for the `serializable_classes` option in
`config/cache.php`.

[ohnotnow]

❌ Shift detected a PHP version constraint of ^8.2 in your composer.json file. Laravel 13 requires PHP 8.3 or higher. Shift bumped your PHP dependency to make your application compatible. However, if you encounter PHP errors, you should review the Migration Notes to ensure your PHP code is compatible.

[ohnotnow]

ℹ️ Shift updated your dependencies for Laravel 13. While many of the popular packages are reviewed, you may have to update additional packages in order for your application to be compatible with Laravel 13. Watch dealing with dependencies for tips on handling any Composer issues.

The following dependencies were updated by a major version and may have their own changes. You may check their changelog for any additional upgrade steps.

• barryvdh/laravel-debugbar
• laravel/boost

The following dependencies were not updated by Shift and may be incompatible. If Composer lists one of these packages as a problem, you should check for a newer version.

• livewire/flux-pro
• ohffs/simple-spout

[ohnotnow]

ℹ️ Shift detected you are running Livewire 3. While this is compatible with Laravel 13, Shift recommends upgrading. Once you have a verified your Laravel upgrade, you may run the Livewire 4.x Shift to upgrade to Livewire 4.

[ohnotnow]

ℹ️ Laravel added an index to the expiration column of the caching tables. Shift did not detect this index, so it created a migration to add it. If this index is missing, you may run this migration with php artisan migrate to add it. Otherwise, you may delete this migration.

[ohnotnow]

ℹ️ Laravel 13 changed the password reset mail subject from "Reset Password Notification" to "Reset your password". If your application relied on the previous subject, for example in custom translation messages, you should update them accordingly.

[ohnotnow]

⚠️ Shift detected you are using a Laravel package like Horizon or Nova which may need to have its published assets regenerated after upgrading. Be sure to use artisan to republish these assets as well as php artisan view:clear to avoid any errors.

[ohnotnow]

🎉 Congratulations, you're now running the latest version of Laravel!

Next, you may optionally run the following Shifts to ensure your application is fully upgraded, adopts the latest Laravel conventions, and easier to maintain in the future:

• Laravel Fixer automatically updates your code to the latest Laravel conventions.
• Tests Generator intelligently generates model factories, HTTP Tests, and configuration for your application.
• CI Generator intelligently generates CI jobs to lint PHP, check code style, and run tests, including Dusk.

You may also use the Shift Workbench to automate common tasks for maintaining your Laravel application.