-
-
Notifications
You must be signed in to change notification settings - Fork 203
Laravel 12.x Shift #2099
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Laravel 12.x Shift #2099
Conversation
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.
|
ℹ️ Starting with Laravel 10, the 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 |
|
You should review this commit for additional customizations or opportunities to use new |
|
ℹ️ Shift detected customized options within your configuration files which may be set with an LOG_CHANNEL=stderrNote: some of these may simply be values which changed between Laravel versions. You may ignore any |
1 similar comment
|
ℹ️ Shift detected customized options within your configuration files which may be set with an LOG_CHANNEL=stderrNote: some of these may simply be values which changed between Laravel versions. You may ignore any |
|
|
|
|
Shift did not detect a |
|
ℹ️ Laravel added a Shift has added this script, as well as the necessary packages. Once you run |
|
ℹ️ In a minor release of Laravel 11, the Shift added the |
|
ℹ️ Starting with Laravel 11, |
|
ℹ️ 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 updated by a major version and may have their own changes. You may check their changelog for any additional upgrade steps. 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. |
|
ℹ️ All of the underlying Symfony components used by Laravel have been upgraded to Symfony 7.2. Shift detected references to Symfony classes within your application. These are most likely type hints and can safely be ignored. If you are using Symfony classes directly or experience issues relating to Symfony, you should review the Symfony change log for any additional changes. |
|
ℹ️ 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. |
|
Unlocked Livewire, seems Filament has addressed the issue: filamentphp/filament#15559 |
This pull request includes the changes for upgrading to Laravel 12.x. Feel free to commit any additional changes to the
shift-144216branch.Before merging, you need to:
shift-144216branchcomposer 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.