$ the-wire · showcase
LARAVEL 13 TIGHTENS REDIS CONFIG AND QUEUE TESTING
By RepoJournal · Filed · About Laravel · Composed from the cited sources · methodology
The framework now supports scalar Predis retry configuration, making it cacheable for the first time, while new queue fake methods let you inspect reserved jobs without reaching for mocks.
Laravel 13 shipped two critical framework improvements overnight that fix real production pain points. First, Predis retry configuration [1] no longer requires instantiating objects, meaning you can safely call `config:cache` without losing your retry strategy. This eliminates a common gotcha where Redis configuration objects would silently fail to serialize. Second, the queue fake [2] now supports `reserve()`, `reservedJobs()`, and `allReservedJobs()`, letting you test job reservation behavior without mocking. The installer [3] also rolled v5.30.0 with a no-node flag [4] that skips npm entirely for headless projects. On the docs front, Cashier now has comprehensive Payment Element integration [6] covering subscriptions, single charges, and payment method updates. A quick onboarding experiment [5] is in progress to reduce setup friction.
Action items
- → Update to framework 13.x to use Predis scalar config with config:cache laravel/framework [plan]
- → Refactor queue tests to use Queue::reserve() instead of mocking laravel/framework [plan]
- → Review Payment Element docs if you're on Cashier Stripe laravel/docs [monitor]
References
- [1] [13.x] Supports scalar Predis retry config to allows `config:cache` ↗ laravel/framework
- [2] [13.x] Support inspecting reserved jobs on the queue fake ↗ laravel/framework
- [3] v5.30.0 ↗ laravel/installer
- [4] v5.29.0 ↗ laravel/installer
- [5] Quick onboard ↗ laravel/installer
- [6] Add Payment Element integration documentation ↗ laravel/docs
