Caption: InteractsWithData.php, MigrationFailed.php, and Migrator.php are the same bytes on v13.41.0, v13.42.0, and v13.43.0. The 13.43 composer change is a conflict with laravel/horizon below 5.47.0.
Introduction
The 11 Nov post left these helpers alone. I am writing this on 18 Nov 2026 (2026-W47). The queue row is 2026-W46, priority 9, the lowest undone item. Nothing is tagged 2026-W47. Laravel News covered them on 11 Nov 2026 and called the release 13.42. Packagist this morning is v13.43.0. I read tags v13.40.0 through v13.43.0. I did not boot the throwaway app.
About the feature
uuid() and ulid() live on Illuminate\Support\Traits\InteractsWithData. Illuminate\Http\Request gets them through InteractsWithInput. The same trait is on ValidatedInput, Fluent, UriQueryString, ComponentAttributeBag, and CommandInput.
Both methods return null when isNotFilled($key) is true: a missing key, '', or whitespace. A boolean or an array counts as filled. A real value goes to Ramsey\Uuid\Uuid::fromString() or new Symfony\Component\Uid\Ulid(). The framework test uses a0a2a2d2-0b87-4a18-83f2-2529882be2de and 01ARZ3NDEKTSV4RRFFQ69G5FAV. Uppercase UUID and lowercase ULID compare equal. 'invalid' throws, and so does ulid() on that UUID.
The requests docs, retrieved 18 Nov 2026, already have this section. They say a missing value is null and an invalid value throws InvalidArgumentException. They do not say '' is null. The test does.
MigrationFailed is dispatched in Migrator::runMigration(). The catch builds new MigrationFailed($migration, $method, $name, $e) and then throw $e. The event has the same migration, method, and name properties as the other migration events, plus exception. runUp() sets $name with getMigrationName(), which is the file basename without .php. The migrations docs list MigrationFailed in the events table. They do not mention the exception property or the rethrow. That is the method body, PR #62342, and the Laravel News piece on 11 Nov.
Caption: The red lines are the invalid branch only. A valid UUID returns Ramsey\Uuid\UuidInterface. safe() is on FormRequest and Validator, not on Illuminate\Http\Request.
Why I picked it
Order ids in this app are UUIDs. Event ids from the check-in scanner are ULIDs. I had been reading both with $request->string() and then Uuid::fromString() in the controller. The helpers are that cast, next to date() and enum(). The failure I care about is calling the wrong one. ulid() does not turn a UUID into a ULID.
MigrationFailed is the other half of the same tags. I already see the process exit code. I want the migration name and the exception class before that exit, including on MySQL, where the first ALTER is not inside a Laravel schema transaction.
Where it can be used
I would call uuid() and ulid() only after validation. The uuid rule calls Str::isUuid() and returns false. The ulid rule calls Str::isUlid() and returns false. Neither throws. The helpers throw. A FormRequest is the place that has safe(), which returns ValidatedInput, which has the trait. A controller type-hinted as Illuminate\Http\Request has uuid() and does not have safe().
MigrationFailed is for php artisan migrate and migrate:rollback when up() or down() throws. migrate --pretend returns from pretendToRun() and never calls runMigration(), so the listener stays quiet. I would not use pretend as the test of this event.
Uri::origin() is the comparison when the path must not count. The slow-task hook from the 11 Nov post still ignores skipped tasks.
Benefit
The helpers, the event, Uri::origin(), and the skip-reason enum are all in laravel/framework. v13.43.0 composer.json requires php: ^8.3, nesbot/carbon: ^3.8.4, league/uri: ^7.6, ramsey/uuid: ^4.7, and symfony/uid: ^7.4.0 || ^8.0.0. replace sets illuminate/http, illuminate/database, and illuminate/console to self.version. I do not composer require illuminate/http.
InteractsWithData.php is identical on v13.41.0, v13.42.0, and v13.43.0. So are MigrationFailed.php, Migrator.php, Uri.php, and ScheduledTaskSkipReason.php. On v13.40.0 those helpers and the event are absent. v13.43.0 keeps the 13.42 require block and adds a conflict on laravel/horizon older than 5.47.0. I would bump to 13.43.0. Packagist still lists 13.41.0 and 13.42.0 from 10 Nov, and composer update lands on 13.43.0. Laravel News has no 13.43 note through 17 Nov. The 13.42 GitHub release body is empty, and the Releases API for tag v13.41.0 returns 404. The tag exists.
Caption: ramsey/uuid is ^4.7. symfony/uid is ^7.4.0 || ^8.0.0. Do not add an illuminate package. Horizon older than 5.47.0 will not solve against 13.43.0.
Practical example from a recent application
Lab shape from the queue notes and tag v13.43.0. If composer show laravel/framework still says 13.40.x, stop. The methods are not on that tag.
composer show laravel/framework | sed -n '1,8p'
# name : laravel/framework
# versions : * v13.43.0
Failure I hit if the order id is a ULID and I call uuid() anyway. Uuid::fromString() lowercases the string, the UUID regex misses, and ramsey/uuid 4.7.6 StringCodec throws Ramsey\Uuid\Exception\InvalidUuidStringException. That class extends Ramsey's InvalidArgumentException, which extends PHP's. For the framework test ULID the message is:
Invalid UUID string: 01arz3ndektsv4rrffq69g5fav
The other direction is the one I would actually ship wrong. ulid() on the test UUID throws Symfony\Component\Uid\Exception\InvalidArgumentException, which extends PHP's InvalidArgumentException. Symfony uid 7.4.0 and 8.0.0 both format it as:
Invalid ULID: "a0a2a2d2-0b87-4a18-83f2-2529882be2de".
I did not execute either call. The framework test catches InvalidArgumentException for both, and those constructors are the messages. Skipping the rules means a 500, not a validation error. The fix is the rule first, then the helper on validated input.
safe() is not on the base request. FormRequest::safe() and Validator::safe() return ValidatedInput. Copying the Laravel News snippet onto Illuminate\Http\Request hits Macroable:
BadMethodCallException: Method Illuminate\Http\Request::safe does not exist.
namespace App\Http\Requests;
use Illuminate\Foundation\Http\FormRequest;
use Ramsey\Uuid\UuidInterface;
class StoreCheckInRequest extends FormRequest
{
public function rules(): array
{
return [
'order_id' => ['required', 'uuid'],
'event_id' => ['required', 'ulid'],
];
}
public function orderId(): UuidInterface
{
return $this->safe()->uuid('order_id');
}
}
After safe(), a valid value is the typed object. An invalid string never gets there: uuid and ulid fail the request first.
Failure I hit if I treat MigrationFailed as a rollback. The listener runs, then the original exception is thrown again, and migrate still exits non-zero. Postgres and SQL Server set supportsSchemaTransactions() true, and Migration::$withinTransaction defaults to true, so runMigration() uses $connection->transaction(). MySQL, MariaDB, and SQLite leave $transactions false. A statement that already ran stays applied.
use Illuminate\Database\Events\MigrationFailed;
use Illuminate\Support\Facades\Event;
use Illuminate\Support\Facades\Log;
Event::listen(function (MigrationFailed $event): void {
Log::critical('migration failed', [
'name' => $event->name,
'method' => $event->method,
'exception' => $event->exception::class,
'message' => $event->exception->getMessage(),
]);
});
$event->name looks like 2026_11_18_120000_add_event_id_to_orders_table. If this listener throws, throw $e never runs.
Caption: migrate --pretend never reaches this catch. Postgres and SQL Server can still skip the transaction when the migration sets $withinTransaction = false.
Same tags, not this lab. Uri::of('https://A.com:443/x')->origin() is https://a.com in SupportUriTest. A relative path, mailto:, and file: return null. The URL docs, on 18 Nov 2026, have no origin() section. ScheduledTaskSkipReason is condition_not_met, paused, or ran_on_another_server.
The 13.43.0 release notes also include security fixes. I am not walking through them and I am not inventing a CVE number. laravel/horizon older than 5.47.0 conflicts with framework 13.43.0 (PR #62449). Packagist has Horizon v5.52.0, published 17 Nov 2026. 5.47.0 is the floor that conflict allows.
Conclusion
What I would keep: laravel/framework at 13.43.0, order_id validated as uuid and event_id as ulid, then safe()->uuid() and safe()->ulid() on a FormRequest. MigrationFailed logs the migration basename and the exception class, and it does not pretend MySQL rolled back. Horizon on that app is 5.47.0 or newer before the framework bump. Next I would point Uri::origin() at the check-in redirect allowlist, where a path difference must not count as a different host.
Did you hit the same wall?
I got stuck on ulid() throwing Invalid ULID: "a0a2a2d2-0b87-4a18-83f2-2529882be2de". when the client sent a UUID, and on BadMethodCallException: Method Illuminate\Http\Request::safe does not exist. Did you hit the same thing — an empty string that came back as null, a MigrationFailed listener that still left the first MySQL ALTER in place, or Composer refusing laravel/horizon below 5.47.0? Tell me in the comments. I read them.
Need this done on your server?
I deploy and harden Laravel/CodeCanyon apps on cPanel or VPS, and offer monthly Server Watch retainers. Hire for deploy · Care plan
References
- Laravel 13.x requests, retrieved 18 Nov 2026. "Retrieving UUID and ULID Input Values" says a missing value returns null and an invalid value throws
InvalidArgumentException: https://laravel.com/docs/13.x/requests - Laravel 13.x migrations, retrieved 18 Nov 2026. The events table lists
MigrationFailedand does not describe theexceptionproperty or the rethrow: https://laravel.com/docs/13.x/migrations - Laravel 13.x scheduling, retrieved 18 Nov 2026. The task-event list includes
ScheduledTaskSkippedand notScheduledTaskSkipReason: https://laravel.com/docs/13.x/scheduling - Laravel 13.x URLs, retrieved 18 Nov 2026. The page has
Uri::ofand noorigin()section: https://laravel.com/docs/13.x/urls - Laravel News, 11 Nov 2026, "UUID Request Input and Migration Failure Events in Laravel 13.42": https://laravel-news.com/laravel-13-42-0
- PRs #62327, #62348, #62342, #62294, #62326, #62316, #62449
- Tags
v13.40.0throughv13.43.0. On 13.41 through 13.43,InteractsWithData.phpSHA-256 isf1b06f1fbc14e3c6205b8ed06560bea3a364bed40e35cd6495dd8ac0e964bdf8,MigrationFailed.phpis3bc138d734e20cc3670e3d8da1f20a0e053ee4f28058c4b43e9b8888df418473, andMigrator.phpiscd48da4548cf5b39bdeabab73b2123b4a2e5dc6227f6f9fde4a11b0d259929f2. Absent on 13.40. Packagist v13.41.0 time 10 Nov 2026 15:44 UTC. v13.42.0 time 15:54 UTC, GitHub release 15:56 UTC. v13.43.0 time 17 Nov 2026 14:58 UTC, GitHub release 15:00 UTC. The Releases API forv13.41.0returns 404: https://packagist.org/packages/laravel/framework - v13.43.0
composer.json:php: ^8.3,nesbot/carbon: ^3.8.4,league/uri: ^7.6,ramsey/uuid: ^4.7,symfony/uid: ^7.4.0 || ^8.0.0.replacesetsilluminate/httptoself.version. Conflict:laravel/horizonolder than 5.47.0.laravel/horizonv5.52.0 time 16 Nov 2026 15:32 UTC. No CVE number is claimed here.