Laravel 13.42 gives request input typed UUID and ULID helpers
New uuid() and ulid() methods return real objects instead of strings, and a MigrationFailed event lets you react to a broken migration as it happens.
Laravel 13.42.0, released on 10 November, adds two request-input helpers that sit alongside the existing date() and enum() methods: uuid() and ulid(). Both return a typed object rather than a string, or null if the field is missing or empty.
$request->uuid('order_id'); // Ramsey\Uuid\UuidInterface|null
$request->ulid('order_id'); // Symfony\Component\Uid\Ulid|null
Because the methods live on the shared InteractsWithData trait, they also work on validated input, Fluent, Uri query strings, component attributes and console command input, not just the request object. The same release adds a MigrationFailed event that fires when a migration throws, so you can react to a broken migration instead of finding out from a support ticket:
Event::listen(function (MigrationFailed $event) {
Artisan::call('down');
});
It also ships a LostConnectionDetector::detectUsing() hook for recognising a dropped database connection without subclassing the connector, and Uri::origin() for comparing two URLs’ origins directly.
Why it matters: pulling a UUID or ULID out of request input used to mean parsing a string yourself and hoping the format was right. These helpers hand back a real, validated object or null, and the same handling now applies everywhere Laravel already deals with “data”, not just HTTP requests.