I Couldn't Fix the Bug Until I Stopped Supporting the Old Major
php
dev.to
TL;DR — laravel-scheduler-manager now targets Livewire 4 only. Not because Livewire 3 stopped working, but because one of the two Livewire 4 bugs had a fix that was unsafe on Livewire 3. Supporting both majors meant shipping neither fix. The compatibility shim wasn't costing me guard code — it was costing me the repair. Where this left off Yesterday I wrote about a constraint I shipped without verifying: the package pinned livewire/livewire to ^3.7 and the README said Livewire 4 w