Two fixes to the make:crud generator. There are no new features.
Generated controllers had the same defect fixed in the abstract CrudController in 1.5.5. The update rule was rebuilt from only the table and column, and the unique segment was moved to the end of the rule string:
required|unique:posts,slug|max:20
before: required|max:20|unique:posts,slug,ID
after: required|unique:posts,slug,ID|max:20
required|unique:users,email,NULL,id,tenant_id,7
before: required|unique:users,email,ID
after: required|unique:users,email,ID,id,tenant_id,7
Per-tenant uniqueness silently became global. Only the ignore-id slot is replaced now, and rule order is preserved. See Update, Unique Ignore.
The enum type generated $table->enum('name', []), a column no database accepts. Values are now declared in the type, separated by pipes:
php artisan make:crud Post --fields="status:enum(draft|published|archived):required"
An enum with no values falls back to a string column with a warning.
--fields separates fields with commas, so a rule that itself contains a comma, such as unique:users,email or in:a,b, cannot be expressed through it. That means the where-clause fix above cannot yet be reached from the command line. It is addressed by --field in 1.5.7.
Controllers and migrations generated before 1.5.6 are unaffected, since these fixes apply at generation time. Regenerate with --force, or edit affected unique rules and enum columns by hand.
The suite grew from 245 to 255 tests, passing in CI across Laravel 10 to 13.