The Wire · Showcase
LARAVEL 13 DETACHES QUEUES FROM SQS, ROUTES THROUGH CLOUD AGENT
By RepoJournal · Filed · About Laravel
Laravel Cloud's managed queue system now intercepts job processing entirely, popping from an in-container agent instead of SQS directly, shifting visibility and deletion logic into the platform layer.
The framework's queue dispatcher now routes through Laravel Cloud's managed-queue agent when enabled, using a unix-socket runtime API instead of hitting SQS directly [1]. The cloud agent long-polls SQS and owns terminal operations; your worker just processes and reports outcomes back. This is infrastructure consolidation that matters if you're running on Cloud: simpler worker logic, unified job lifecycle management, and one less place your code needs SQS permissions. Meanwhile, the string utilities are getting nicer [2]: the new `counted()` method solves the annoying pattern of prepending counts to pluralized strings without storing variables twice. Collections are also getting `reduceInto()` [3], a mutation-based reduce that reads cleaner than accumulating and returning in traditional reduce patterns. These are quality-of-life wins, not breaking changes. Dusk's action workflow got a minor bump [4] but nothing that impacts your test suites.
Action items
- → If you're on Laravel Cloud with managed queues enabled, verify your workers are picking up the new agent-routed pop logic in 13.x laravel/framework [plan]
- → Audit queue job deletion and visibility timeout handling if you've customized SqsQueue behavior laravel/framework [monitor]
- → Refactor pluralization patterns using the new `counted()` method in string utilities laravel/framework [monitor]
References
- [1] [13.x] Pop managed queue jobs from the cloud-agent instead of SQS ↗ laravel/framework
- [2] [13.x] Add `counted` method to `Str` and `Stringable` ↗ laravel/framework
- [3] [13.x] Add `reduceInto` method to collection ↗ laravel/framework
- [4] Bump stefanzweifel/git-auto-commit-action from 7.1.0 to 7.2.0 in the github-actions group ↗ laravel/dusk
FAQ
- What changed in Laravel on July 4, 2026?
- Laravel Cloud's managed queue system now intercepts job processing entirely, popping from an in-container agent instead of SQS directly, shifting visibility and deletion logic into the platform layer.
- What should Laravel teams do about it?
- If you're on Laravel Cloud with managed queues enabled, verify your workers are picking up the new agent-routed pop logic in 13.x • Audit queue job deletion and visibility timeout handling if you've customized SqsQueue behavior • Refactor pluralization patterns using the new `counted()` method in string utilities
- Which Laravel repositories shipped on July 4, 2026?
- laravel/framework, laravel/dusk