Skip to content
This repository was archived by the owner on Aug 12, 2021. It is now read-only.

Conversation

@MarcyLina
Copy link

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

Before merging, you need to:

  • Checkout the shift-43397 branch
  • Review all pull request comments for additional changes
  • Update your dependencies for Laravel 5.7
  • Run composer update (if the scripts fail, add --no-scripts)
  • Clear any config, route, or view cache
  • Thoroughly test your application (no tests?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

PHP 5.5.9+ adds the new static `class` property which provides the fully qualified class name. This is preferred over using class name strings as these references are checked by the parser.
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.
@MarcyLina
Copy link
Author

⚠️ Laravel 5.7 changed the environment variable QUEUE_DRIVER to QUEUE_CONNECTION. Shift automated this change. However, you should review this server configuration or .env files outside your project to see if they need to be changed.

@MarcyLina
Copy link
Author

MarcyLina commented Apr 6, 2021

⚠️ Since you are upgrading from an older version of Laravel, Shift defaulted your customized configuration files to improve the automation in your next Shift. This was done in a separate commit so you may easily reference the changes and backfill your customizations once you are done Shifting. Future Shifts (Laravel 6+) will preserve your true customizations by merging them back in with the defaults.

  • config/database.php
  • config/services.php

@MarcyLina
Copy link
Author

ℹ️ Laravel 5.7 removed the Blade "or" operator in favor of PHP's built-in ?? "null coalesce" operator.

Shift automated this change. However, your application may still contain instances of or if you are using Blade syntax outside of the resources folder.

@MarcyLina
Copy link
Author

❌ Laravel 5.7 has a dependency for php of ^7.1.3. You have a modified dependency for php in your composer.json. You should review your dependency and ensure it meets the new version requirement.

@MarcyLina
Copy link
Author

❌ Laravel 5.7 has a development dependency for mockery/mockery of ^1.0. You have a modified dependency for mockery/mockery in your composer.json. You should review your dependency and ensure it meets the new version requirement.

@MarcyLina
Copy link
Author

ℹ️ Laravel 5.7 removed the resources/assets folder in favor of placing its sub-folders directly under resources. Shift moved these for you automatically. However, you may need to update the paths configured in your frontend build tool (e.g. webpack.mix.js) to reflect this new structure.

While Shift encourages a fully upgraded application, this new structure is not required. If this change significantly impacts your frontend build process, you can revert this commit.

@MarcyLina
Copy link
Author

ℹ️ Laravel 5.7 now supports email verification when users register for your application. If you have implemented this feature yourself you may now be able to take advantage of this native functionality. For more details, review the documentation on Email Verification.

@MarcyLina
Copy link
Author

⚠️ Laravel 5.7 has reached end of life. It no longer receives bug fixes or security updates. Shift recommends continuing to upgrade to the latest LTS version (Laravel 6.x) or latest stable version (Laravel 8.x). For tips on running multiple Shifts effectively, watch upgrading old Laravel applications.

@mattstauffer
Copy link
Member

@MarcyLina could you take a look, when you have a free moment (no rush), at why the tests are failing? Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants