Laravel 13.42.0
The Laravel team shipped framework release 13.42.0 on November 10, 2026, a maintenance cut that closes out a busy fortnight of pull requests. The release is the second since 13.40.0 and carries no configuration changes, but it includes a security-relevant fix to token authentication and several additions aimed at API and database work.
What Changed
The most consequential item sits in TokenGuard. Validation now hashes the presented token when hashing is enabled, closing a gap between how tokens are stored and how they were compared. Applications using hashed API tokens should treat the upgrade as a security update rather than a routine bump.
Database handling received several adjustments. A failed commit caused by a lost connection now discards the PDO instance instead of leaving a dead handle in the pool, and the lost connection detector exposes detectUsing() so applications can define their own failure check. On PostgreSQL, dropping all views now ignores views owned by extensions, and foreignIdFor() accepts an integer key type.
Testing and attribute handling gained two conveniences: uuid() and ulid() are available on InteractsWithData, which trims boilerplate from request payload tests.
The Rest of the List
- Scheduled tasks gain
ScheduledTaskSkipReason, giving skip outcomes a typed representation. - Events include a new
MigrationFailedevent, useful for alerting when a deployment migration fails. - Processes can now use the
Macroabletrait throughPendingProcess. - URIs expose
origin()for assembling scheme, host, and port in one call. - JSON:API compound documents include identical
BelongsToManyresources only once. - Lazy loading prevention is respected when iterating multiple models with
cursor(). - Collections accept
ArrayAccessreturn values fromArr::push(). - Sessions substitute invalid UTF-8 during JSON encoding instead of throwing.
- Broadcasting fixes Pusher authentication for invalid channel names and adds support for
ably/pubsub-server2. - Queues correct job ID and property types on
BeanstalkdJob. - SQLite grammar return types for
dropPrimaryanddropForeignare corrected.
Why It Matters
Point releases in the 13.x line rarely change behavior, and this one behaves predictably: the changes are narrow, and none of them require a migration. The token hashing fix is the reason to move promptly. The remaining items remove small classes of confusing failures, particularly around connections that die mid-transaction and around view cleanup on managed PostgreSQL instances.
The framework also continues an internal shift visible in this window: the test suite moved from Mockery to a double-based approach, and facade docblocks were regenerated. Neither affects application code, but both signal ongoing cleanup work inside the repository.
What's Next
Upgrade with composer update laravel/framework after reviewing the diff against 13.41.x. If you rely on custom token guards, verify that hashed comparison behaves as expected in staging before shipping to production. Teams still on 12.x remain supported, though the 13.x line is where new framework work lands.