$ the-wire · showcase
Container fixes SelfBuilding stack leak, Horizon cluster tests stabilized
By RepoJournal · Filed · About Laravel
3 people shipped this
Laravel's container now cleans up the SelfBuilding build stack even when a factory throws, and Horizon's Redis Cluster CI jobs no longer race on a shared temp file.
The Laravel framework container now cleans up the build stack after a `SelfBuilding::newInstance()` factory throws. Previously, an exception left the class on the stack, so resolving the same class again skipped the factory and went straight to the constructor; the cleanup now runs in a `finally` block, preserving successful resolution and callback order. [1]
Horizon's Redis Cluster integration tests were failing intermittently because all three cluster nodes daemonized from the same working directory. Redis 7 writes its AOF to "<dir>/appendonlydir" and stages the manifest through a fixed "temp-appendonly.aof.manifest" name, so the nodes raced to rename one shared temp file; giving each node its own directory fixes it. [2]
Laravel Echo's 2.x branch upgrades to pnpm 12 and runs `pnpm audit --fix update` to resolve vulnerabilities, keeping the pipeline green. [3]
Action items
- → If you rely on SelfBuilding factories, add the container fix to your framework fork or watch for it in the next release. laravel/framework [monitor]
- → No action needed for Horizon CI failures unless you maintain your own cluster test setup; the fix is already merged. laravel/horizon [monitor]
- → No action needed for Echo users; this is a development dependency upgrade. laravel/echo [monitor]
References
- [1] [13.x] Fix SelfBuilding build stack cleanup after exceptions ↗ laravel/framework
- [2] Fix Redis Cluster tests in the CI (#1817) ↗ laravel/horizon
- [3] [2.x] Upgrade to pnpm 12 and resolve vulnerabilities ↗ laravel/echo
