Laravel 10.x Shift#33
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 them since they did not contain any 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 |
|
ℹ️ Laravel 10 now verifies hashed values were created by the same hashing algorithm. If your application has hashed values created by different hashing algorithms, you may set the |
|
ℹ️ Shift updated your dependencies for Laravel 10. 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 10. 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. |
|
ℹ️ Laravel renamed the |
|
ℹ️ Laravel 10 added PHP type hints to all user-land code included in a new Laravel application. In an effort to modernize your code, Shift added type hints to any method which is used by Laravel. |
|
ℹ️ Now with type hints in your code, defining types within PHP DocBlocks is redundant. Laravel has removed all of the |
|
ℹ️ Shift understands developers have different preferences when it comes to type hints. All of Shift's automation is done in nice, atomic commits. This makes it easier to undo any of the changes Shift makes. If you wish to undo the changes relating to type hints, you may run:
|
|
ℹ️ All of the underlying Symfony components used by Laravel have been upgraded to Symfony 6.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. |
|
ℹ️ The If you wish to modernize your application to use the |
|
ℹ️ Laravel began using Vite to build frontend assets in Laravel 9.19. While you may continue to use Laravel Mix, it is no longer the default. If you wish to modernize your application to use Vite, you may run the Vite Converter for free. |
|
|
|
|
|
|
This pull request includes the changes for upgrading to Laravel 10.x. Feel free to commit any additional changes to the
shift-157061branch.Before merging, you need to:
shift-157061branchcomposer update(if the scripts fail, try with--no-scripts)If you need help with your upgrade, check out the Human Shifts.