Shift with red gradient lettering

Upgrade Laravel 5.0 to Laravel 5.1

The Laravel 5.1 Shift automates the upgrade of your Laravel application from Laravel 5.0 to Laravel 5.1. Using the Laravel 5.1 Shift to automatically upgrade your Laravel application has an estimated time savings of 2 hours.

Laravel 5.1 has reached end of life. It no longer receives bug fixes or security updates. Shift strongly recommends continuing your upgrade to the latest LTS release or latest stable release of Laravel. Watch upgrading old Laravel applications for tips on running multiple Shifts effectively.

Screenshot of a pull request with atomic commits for each change of the Laravel 5.1 Shift

Requirements

  • A Laravel application running Laravel 5.0.x.

Core Upgrades

The Laravel 5.1 Shift automates many of the upgrades listed in the Laravel Upgrade Guide, including:

  • Migrating translation files to their new folder structure.
  • Upgrading Commands and Events classes to Job and Listeners, respectively.
  • Changing the method signatures on Eloquent's create and find methods.
  • Upgrading the Authentication classes for Laravel 5.1.
  • Creating and configuring the new bootstrap/cache folder.
  • Upgrading object references for Laravel 5.1, e.g. remove BusServiceProvider.
  • Adding the new app/Policies in Laravel 5.1.

Additional Upgrades

In addition to the Core Upgrades, the Laravel 5.1 Shift performs additional upgrades beyond those listed in the Laravel Upgrade Guide, including:

  • Adopting the Laravel code style.
  • Upgrading bindings to take advantage of the PHP 5.5 ::class property.
  • Changing instances of RedirectResponse to use the redirect method directly.

Manual Upgrades

There are some upgrades the Laravel 5.1 Shift can not perform automatically. When Shift detects these it adds a detailed comment on the Pull Request to help guide any additional upgrade steps.

  • Several of the Collection methods changed in Laravel 5.1. Given the dynamic nature of PHP and the various ways to implement these methods in Laravel, Shift can not reliably update these method calls automatically.
  • Blade extensions changed in Laravel 5.1. Shift can not reliably convert to the new directive method.

Sign in with any of the following services to connect Shift with your Laravel project.

Don't use one of these services?

Temporarily push your project to a free, private repository on one of these cloud-based services or upgrade your project locally with Shift for Docker.