-
Notifications
You must be signed in to change notification settings - Fork 16
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 11.x Shift #318
base: develop
Are you sure you want to change the base?
Laravel 11.x Shift #318
Conversation
ℹ️ To slim down the Laravel installation, Laravel 11 no longer has most of the core files previously included in the default Laravel application. While you are welcome to publish and customize these files, they are no longer required. Shift takes an iterative approach to removing core files which are not customized or where its customizations may be done elsewhere in a modern Laravel 11 application. As such, you may see some commits removing files and others re-registering your customizations. |
❌ Shift could not upgrade the following files since they differed from the default Laravel version. You will need to compare these files against the default Laravel 11 versions and merge any changes:
|
Shift detected your version differed from the default Laravel version. If you have customized the password validation messages, you should merge them with the |
ℹ️ Laravel 11 no longer requires you to maintain the default configuration files. Your configuration now merges with framework defaults. Shift streamlined your configuration files by removing options that matched the Laravel defaults and preserving your true customizations. These are values which are not changeable through If you wish to keep the full set of configuration files, Shift recommends running |
ℹ️ Shift detected customized options within your configuration files which may be set with an ARGON_MEMORY=1024
ARGON_THREADS=2
ARGON_TIME=2
BCRYPT_ROUNDS=10
CACHE_STORE=file
DB_CONNECTION=mysql
MAIL_MAILER=smtp
QUEUE_CONNECTION=sync
SESSION_DRIVER=file Note: some of these may simply be values which changed between Laravel 10 and Laravel 11. You may ignore any |
Shift automated this change for your committed files, but you should review any additional locations where your environment is configured and update to the new variable names. |
❌ The |
Shift detected event listeners registered with the |
You should review your custom routes to see if you need to use one of these callbacks or if your customizations may be done within the route file. You may reference the documentation on Route Customization for more details on these callbacks. Route::prefix('api')
->group(base_path('routes/api.php'));
Route::group(base_path('routes/jetstream.php'));
Route::group(base_path('routes/fortify.php')); |
$this->app->bind(\Illuminate\Contracts\Debug\ExceptionHandler::class, \App\Exceptions\Handler::class); |
ℹ️ Shift updated your dependencies for Laravel 11. 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 11. 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. |
Shift added the
|
ℹ️ 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: |
ℹ️ The base Shift detected your base controller did not have any public methods, so it was safe to mark as |
Shift detected potential uses of the |
|
php artisan vendor:publish --tag=sanctum-migrations |
ℹ️ Laravel 11 now updates the timestamp when publishing vendor migrations. This may cause problems in existing applications when these migrations were previously published and ran with their default timestamp. To preserve the original behavior, Shift disabled this feature in your |
|
|
ℹ️ All of the underlying Symfony components used by Laravel have been upgraded to Symfony 7.0. 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. |
|
|
|
🎉 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 11.x. Feel free to commit any additional changes to the
shift-119662
branch.Before merging, you need to:
shift-119662
branchcomposer update
(if the scripts fail, try with--no-scripts
)If you need help with your upgrade, check out the Human Shifts.