Skip to content

Laravel 9 Mid-Shift - #83

Open
chaseconey wants to merge 2 commits into
mainfrom
shift-mid-laravel-9
Open

Laravel 9 Mid-Shift#83
chaseconey wants to merge 2 commits into
mainfrom
shift-mid-laravel-9

Conversation

@chaseconey

Copy link
Copy Markdown
Owner

This pull request includes recent changes to Laravel core files. Although some of these changes may be considered optional, they may be required to you use recent additions - such as exception log levels, UUID and ULID support, Precognition, and more.

Since Laravel has moved to an annual release cycle, these changes may reach a critical mass. When they do, you will receive this automated pull request as part of your Shifty Plan.

Before merging, you need to:

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

If you would like more detail you may view the full changes. You may also review the Shifty Bits Newsletter for Laravel release highlights.

@chaseconey

Copy link
Copy Markdown
Owner Author

❌ Shift was not able to automate some of the changes to core Laravel files. You should compare the following files against their latest Laravel 9 versions and merge any changes:

@chaseconey

Copy link
Copy Markdown
Owner Author

⚠️ Shift was not able to automate some of the changes to configuration files. You should compare the following files against their latest Laravel 9 versions and merge any changes:

@chaseconey

Copy link
Copy Markdown
Owner Author

ℹ️ Shift updated your dependencies with the latest constraints from Laravel 9. While many of the popular packages are also reviewed, you may have to update some packages. Watch dealing with dependencies for tips on handling any package incompatibilities.

@chaseconey

Copy link
Copy Markdown
Owner Author

⚠️ Shift detected you are using a Laravel package like Horizon or Nova which may need to have its published assets regenerated after upgrading. Be sure to use artisan to republish these assets as well as php artisan view:clear to avoid any errors.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants