RepoJournal
Laravel

@laravel

PHP's most popular framework — Forge, Vapor, and a massive paying audience

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Thu 14 may
  13. Fri 15 may
  14. Sat 16 may
  15. Sun 17 may
  16. Tue 19 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

LARAVEL 13 GAINS QUEUE RESILIENCE AND NOTIFICATION STORAGE ATTACHMENTS

By RepoJournal · Filed · About Laravel

Laravel 13.12.0 shipped with three critical queue improvements and a new notification attachment API that mirrors mailable storage support.

Two framework releases landed overnight across the 12.x and 13.x lines. The 13.x update [2] brings the headliner: workers can now opt out of automatic restart when database connections drop, giving you fine-grained control over queue resilience. That same release adds the ability to resolve scheduled event callbacks by type instead of name [2], eliminating fragile string-based parameter matching. Version 12.61.0 [1] fixes a real bug where queue:failed was reporting the wrong class name, making failed job debugging substantially less painful. Both versions accept Symfony's new control-characters exception message in mailer tests [1] [2], keeping you aligned with the latest Symfony stack. On the notification front, MailMessage now supports attachFromStorage and attachFromStorageDisk helpers [3], bringing feature parity with mailables and letting you attach files directly from your storage disks without constructing Attachment instances by hand. A parallel improvement to managed queues [4] wraps AWS SDK errors in a new ManagedQueueNotFoundException with clear messaging when a queue vanishes, replacing cryptic AWS exceptions with something debuggable. Minor CI updates landed on Lumen [6] and Dusk [7], plus a developing addition to add uri() to Client/Request [5].

Action items

References

  1. [1] v12.61.0 ↗ laravel/framework
  2. [2] v13.12.0 ↗ laravel/framework
  3. [3] [13.x] Add attachFromStorage helpers to notification MailMessage ↗ laravel/framework
  4. [4] [13.x] Throw ManagedQueueNotFoundException when a managed queue is missing ↗ laravel/framework
  5. [5] Add Client\Request::uri() (#60282) laravel/framework
  6. [6] Bump the github-actions group across 1 directory with 2 updates ↗ laravel/lumen-framework
  7. [7] Bump shivammathur/setup-php from 2.37.0 to 2.37.1 in the github-actions group ↗ laravel/dusk

FAQ

What changed in Laravel on May 27, 2026?
Laravel 13.12.0 shipped with three critical queue improvements and a new notification attachment API that mirrors mailable storage support.
What should Laravel teams do about it?
Upgrade to Laravel 13.12.0 if you run managed SQS queues • Review queue:failed output after upgrading to 12.61.0 or 13.12.0 • Integrate attachFromStorage into notification templates
Which Laravel repositories shipped on May 27, 2026?
laravel/framework, laravel/lumen-framework, laravel/dusk

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.