-
Notifications
You must be signed in to change notification settings - Fork 227
Upgrade to Laravel 7.x #4482
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
Upgrade to Laravel 7.x #4482
Conversation
Since PHP 5.4 the short array syntax `[]` may be used instead of `array()`.
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.
Shift recommends changing this to align with Laravel and improve its automation. After doing so, you are welcome to request a rerun of this Shift. |
❌ Shift was unable to find your Exception Handler. Laravel 7 upgraded to Symfony 5 which passes instances of the You should compare your |
ℹ️ Laravel 7 moved the Authentication components into a separate Shift added this dependency for convenience. However, if you do not plan to use the Authentication components, you may remove this dependency as well as the |
Shift converted usages of |
Shift attempted to automate this change, but you should review any additional environment configuration and update to the new variable name. |
You should review this commit for additional customizations or opportunities to use new |
ℹ️ Shift updated your dependencies for Laravel 7. 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 7. Watch dealing with dependencies for tips on handling any additional package incompatibilities. |
ℹ️ Laravel 7 removed some of the PHPUnit configuration in favor of the defaults. While this is not a required changed, it is a good opportunity to compare your |
If you were manually escaping the values passed to these methods, you no longer need do so. If you were asserting values containing HTML that should not be escaped, you may set the new Shift found the instances of these assertions within:
|
|
This does not affect how dates are stored. Only how they are serialized when using the If you need to preserve the previous format, you may override the |
ℹ️ All of the underlying Symfony components used by Laravel have been upgraded to Symfony 5. If you are directly interacting with any Symfony component, you should review the Symfony change log for additional changes. |
|
For tips on running multiple Shifts effectively, watch upgrading old Laravel applications. |
@caleeli Made those changes, thanks! |
@nolanpro please include Package-versions PR to description https://github.com/ProcessMaker/package-versions/pull/54 |
Closing in favor of #4483 |
Issues
https://processmaker.atlassian.net/browse/FOUR-6564
https://processmaker.atlassian.net/browse/FOUR-6565
Upgrade to Laravel 7
Package PRs
Note: PMQL was locked to version <=6 so I temporarily specified
dev-develop
until there's a new release. I would recommend doing a release then updating this composer.json, then running composer update and committing composer.lock, before merging this PR.Testing:
feature/FOUR-6565
branch for the above packages.Original Laravel Shift PR text below
This pull request includes the changes for upgrading to Laravel 7.x. Feel free to commit any additional changes to the
shift-69390
branch.Before merging, you need to:
shift-69390
branchcomposer update
(if the scripts fail, add--no-scripts
)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.