Laravel 10 Mid-Shift

[mattstauffer]

This pull request includes recent changes to Laravel skeleton files. Although some of these changes may be considered optional, they may be required to use recent additions - such as the hashed attribute cast and log processors. This also includes new configuration options and skeleton slimming.

Since Laravel has moved to an annual release cycle, changes since the initial release 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-10 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 stay informed of weekly Laravel release highlights through the Shifty Bits Newsletter.

[mattstauffer]

ℹ️ Laravel 10.x has introduced a new hashed attribute cast. This ensures a value is hashed before saving. The Laravel skeleton application now casts the user password field as hashed.

If you have a User model with a password field, or other models with hashed values, you may update your model $casts property to set the field as hashed.

protected $casts = [
    'password' => 'hashed',
    // ...
];

[mattstauffer]

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

• app/Exceptions/Handler.php
• app/Providers/AuthServiceProvider.php

[mattstauffer]

ℹ️ Shift updated your dependencies with the latest constraints from Laravel 10. 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.

[mattstauffer]

ℹ️ Laravel added the VITE_APP_NAME environment variable to allow you to customize your application name in frontend components. By default, this uses the value from the APP_NAME environment variable.

Shift added this to your .env files, but you will need to update your frontend components to use this new variable. You may reference the original Breeze PR for examples.