Skip to content

Conversation

driftingly
Copy link
Member

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

Before merging, you need to:

  • Checkout the shift-158384 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.

Shift automatically applies the Laravel coding style - which uses the PSR-12 coding style as a base with some minor additions.

You may customize the code style applied by configuring [Pint](https://laravel.com/docs/pint), [PHP CS Fixer](https://github.com/FriendsOfPHP/PHP-CS-Fixer), or [PHP CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer) for your project root.

For more information on customizing the code style applied by Shift, [watch this short video](https://laravelshift.com/videos/shift-code-style).
In an effort to make upgrading the constantly changing config files easier, Shift defaulted them and merged your true customizations - where ENV variables may not be used.
@driftingly
Copy link
Member Author

ℹ️ Starting with Laravel 10, the lang folder is no longer included in a default Laravel application. Laravel now recursively merges any customizations with framework defaults.

Shift streamlined your language files by removing options that matched the Laravel defaults and preserving your customizations. If you wish to keep the full set of language, Shift recommends running artisan lang:publish --force to get the latest configuration files from Laravel, then reapplying the customizations Shift streamlined.

@driftingly
Copy link
Member Author

⚠️ 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 60028e2d and make the config file changes manually.

@driftingly
Copy link
Member Author

ℹ️ Shift detected customized options within your configuration files which may be set with an ENV variable. To help keep your configuration files streamlined, you may set the following variables. Be sure adjust any values per environment.

LOG_STACK=single,flare
MAIL_HOST=smtp.mailgun.org
MAIL_MAILER=smtp
MAIL_PORT=587

Note: some of these may simply be values which changed between Laravel versions. You may ignore any ENV variables you do not need to customize.

1 similar comment
@driftingly
Copy link
Member Author

ℹ️ Shift detected customized options within your configuration files which may be set with an ENV variable. To help keep your configuration files streamlined, you may set the following variables. Be sure adjust any values per environment.

LOG_STACK=single,flare
MAIL_HOST=smtp.mailgun.org
MAIL_MAILER=smtp
MAIL_PORT=587

Note: some of these may simply be values which changed between Laravel versions. You may ignore any ENV variables you do not need to customize.

@driftingly
Copy link
Member Author

⚠️ The following environment variables have been renamed. Shift did not find these variables referenced in your committed files, but you should review any additional locations where your environment is configured and update to the new variable name.

  • MAIL_ENCRYPTION to MAIL_SCHEME

@driftingly
Copy link
Member Author

⚠️ Laravel 12 removed the APP_TIMEZONE environment variable. The timezone now defaults to UTC. Shift removed this variable from your .env file since it was set to UTC.

Shift detected additional references to the APP_TIMEZONE environment variable in the following files. You should remove the environment variable and, if necessary, reference the app.timezone configuration option instead.

  • config/app.php

@driftingly
Copy link
Member Author

ℹ️ Laravel added a composer run dev script which starts php artisan serve, php artisan queue:listen --tries=1, php artisan pail, and npm run dev all in one command.

Shift has added this script, as well as the necessary packages. Once you run composer update and npm install, you will be able to use the new composer run dev script.

@driftingly
Copy link
Member Author

ℹ️ In a minor release of Laravel 11, the local storage disk was updated to use the storage/app/private folder. This keeps files organized within a subfolder, similar to the public disk.

Shift added the storage/app/private folder. However, to avoid potentially breaking your app, Shift did not change your configuration. If you want, you may migrate your files and update your local disk path in your config/filesystems.php file. If you are not using the local storage disk, you may go ahead and update the path.

@driftingly
Copy link
Member Author

ℹ️ Starting with Laravel 11, guzzlehttp/guzzle is included as a framework dependency. Since Shift did not detect any references to the GuzzleHttp namespace within your application it removed your direct dependency.

@driftingly
Copy link
Member Author

ℹ️ Shift updated your dependencies for Laravel 12. 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 12. Watch dealing with dependencies for tips on handling any Composer issues.

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.

@driftingly
Copy link
Member Author

ℹ️ Laravel 9 adopted anonymous migrations. Shift automated this change to align with modern Laravel conventions and avoid naming migrations.

@driftingly
Copy link
Member Author

ℹ️ Starting with Laravel 10, PHP type hints were added within classes included in a Laravel application. In an effort to modernize your code, Shift automated this change where Laravel strictly specifies a type. If you prefer not to type hint your code you may revert this commit by running: git revert a825b4f0

@driftingly
Copy link
Member Author

ℹ️ If you are using the Laravel installer CLI tool to create new Laravel applications with laravel new, you should updated to the latest version to receive updates for Laravel 12 and the new starter kits.

You may update your installer by running:

composer global require laravel/installer

@driftingly
Copy link
Member Author

⚠️ Laravel 12 no longer includes the SVG image type when performing image validation. If your application allows SVG images, you should review your image validation rules and update them to use the new allow_svg option.

'cover' => ['required', 'image:allow_svg'],
'avatar' => ['required', File::image(allowSvg: true)],

@driftingly
Copy link
Member Author

🎉 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.

@driftingly driftingly merged commit 1217d34 into main Sep 15, 2025
2 checks passed
@driftingly driftingly deleted the shift-158384 branch September 15, 2025 05:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants