Laravel 5.6 Shift

[laravel-shift]

This pull request includes the changes for upgrading to Laravel 5.6. Feel free to commit any additional changes to the shift-6092 branch.

Before merging, you should:

• Checkout the shift-6092 branch
• Review all pull request comments for additional changes
• Update your dependencies for Laravel 5.6
• Run composer update (if the pre-scripts fail, add --no-scripts)
• Thoroughly test your application

If you need help with your upgrade, check out the Shift Human Services or join the Shifty Coders Slack room to get answers to all your Laravel questions.

[laravel-shift]

ℹ Laravel 5.6 introduced a logging configuration file. You should ensure the log and log_level settings previously in the config/app.php are now set in config/logging.php.

[laravel-shift]

⚠ Since Laravel 5.6 has not officially been released, Shift set your dependency to dev-develop. Once Laravel 5.6 is released, you should set your dependency for laravel/framework to 5.6.*.

[laravel-shift]

ℹ All of the underlying Symfony components used by Laravel have been upgraded to Symfony 4.0. If you are directly interacting with Symfony components, you should review the Symfony change log and update your application accordingly.

[laravel-shift]

ℹ The previously deprecated optimize Artisan command has been removed. With recent improvements to PHP itself including the OPcache, the optimize command no longer provides any relevant performance benefit.

[laravel-shift]

ℹ In Laravel 5.6, Blade will double encode special characters by default. If you would like to maintain the previous behavior of preventing double encoding, you may add Blade::withoutDoubleEncoding() to your AppServiceProvider boot method.

[laravel-shift]

ℹ Laravel 5.6 uses Bootstrap 4 by default. Shift did not update your front-end resources or dependencies as this could impact your UI. If you are using Bootstrap and wish to continue using Bootstrap 3, you should add Paginator::useBootstrapThree(); to your AppServiceProvider boot method.

[laravel-shift]

ℹ If you have manually upgraded your app from previous versions of Laravel, you should run the Laravel Linter to ensure your app is fully upgraded to the latest version of Laravel.