Conversation
|
ℹ️ Laravel 12 removed the |
|
If your application uses cache prefixes or session cookies and you were not explicitly setting these ENVs, you may set them to their previous defaults to avoid any unexpected behavior. |
|
|
|
Shift did not detect a |
|
ℹ️ Laravel added a Shift has added this script, as well as the necessary packages. Once you run |
|
ℹ️ Laravel added a |
|
ℹ️ Laravel added a |
|
ℹ️ In a minor release of Laravel 11, the Shift added the |
|
ℹ️ 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. |
|
ℹ️ If you are using the Laravel installer CLI tool to create new Laravel applications with You may update your installer by running: composer global require laravel/installer |
|
'cover' => ['required', 'image:allow_svg'],
'avatar' => ['required', File::image(allowSvg: true)], |
|
ℹ️ The container now respects the default value of constructor parameters when resolving a class instance. If you were previously relying on the container to set a value, you will need to pass in this value when resolving the class instead. |
|
🎉 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:
You may also use the Shift Workbench to automate common tasks for maintaining your Laravel application. |
This pull request includes the changes for upgrading to Laravel 12.x. Feel free to commit any additional changes to the
shift-167632branch.Before merging, you need to:
shift-167632branchcomposer update(if the scripts fail, try with--no-scripts)If you get stuck, never hesitate to email support. If you need more help with your upgrade, check out the Human Shifts.