Laravel 13.39.0
The Laravel team released framework version 13.39.0 on October 27, 2026, a maintenance release for the 13.x line that carries roughly sixty pull requests. There is no new headline feature. The work is spread across the database layer, the queue and scheduler, the test suite, and a handful of security-flavoured fixes around file handling and JSON encoding.
Version 12.70.2 shipped on the same day for applications still on the older branch, and 12.70.1 landed a week earlier on October 21.
What Changed
The most visible addition is an escape hatch on the #[Table] attribute. Models can now opt out of an assumed primary key with #[Table(key: false)], which suits pivot tables, view-backed models, and legacy schemas that have no single-column key. Model creation had to be patched in the same release to respect the flag, so the two changes are worth reading together.
Queue and scheduler work accounts for a large share of the diff. The JobAttempted event now carries a duration, and the sync queue was updated to pass it along as well, which makes per-job timing available without wrapping jobs in your own instrumentation. Database queue jobs no longer fail on concurrency errors raised while reserving a job, and queue:retry now handles non-scalar failed job identifiers instead of erroring out. A job whose model has been deleted no longer blocks queue:retry entirely. schedule:interrupt now fails loudly when interruption polling is disabled rather than silently doing nothing.
Cache and configuration writes became atomic. The config, route, and event cache files are now written atomically, which closes the window where a deploy that reads the cache mid-write could load a truncated file. Two cache bugs were fixed alongside it: the database cache lock no longer aborts an open transaction on PostgreSQL, and cache:prune-stale-tags works correctly with the phpredis SCAN_PREFIX option.
Session handling gained a dedicated command. A SessionGarbageCollectCommand was added and registered as session:garbage-collect, giving deployments a first-class way to prune expired sessions without reaching for a custom artisan command.
On the HTTP client, Http::batch() no longer reports retry() and throw() failures as successes, which was quietly masking failed requests in batched pools.
Eloquent picked up several fixes: forceCreate and forceCreateQuietly are now available on BelongsToMany, pivot columns are qualified inside wherePivot closures, latest() and oldest() behave correctly with a join built from a subquery, and restoreOrCreate() and createOrRestore() now work on relations, including through relations. Pagination counts were corrected for grouped union queries, and the simple paginator no longer ignores a custom page name.
Two file-system changes deserve attention. The phar:// stream wrapper is now blocked in Filesystem::exists() and isFile(), while reading files from the currently running phar is still permitted. That pairing is deliberate: it shuts down a path that could be abused to probe archive contents while keeping Phar-distributed artisan applications working.
JSON handling got stricter. Object casts and JSON path assignments now throw when a value cannot be encoded, instead of writing something unexpected to the column. The distinct:ignore_case rule no longer throws on values that are not valid UTF-8.
Why It Matters
Atomic cache writes and the PostgreSQL lock fix are the two items most likely to affect production behaviour, because both address failure modes that only appear under load or during a deploy. The phpredis broken pipe issue is handled too: the client is rebuilt when a broken pipe surfaces as a warning rather than an exception, which prevents stale connections from poisoning a long-running worker.
Testing saw concrete improvements. RefreshDatabase now rolls back all transaction levels after each test, which fixes leaking state in suites that open nested transactions. MailFake can fake html() and plain(), BusFake gained withoutDispatchingAfterResponses, and process fakes accept exit code and exception shorthands. A new WithoutMigrationEvents attribute rounds out the migration tooling. The assertSeeText('0') assertion no longer passes silently when the string zero is expected.
Elsewhere: view namespace hints are resolved the same way as view locations, the previous route no longer leaks into 404 requests under Octane, Request::route() has a correct return type when no route resolves, illuminate/bus no longer fatals when illuminate/queue is absent, and the transactions manager rolls back correctly when a commit fails.
What's Next
Patch releases on the 13.x line arrive weekly, and 13.39.0 is a standard drop-and-test update. Run the suite, pay attention to any custom queue instrumentation that reads JobAttempted, and check whether your project relies on phar:// paths outside the running archive.
Upgrade with composer update laravel/framework and review the pull request list for the full accounting.