Livewire 4.3.3

Livewire 4.3.3 — The Verdict

I've been running Livewire 4.3.3 on a Laravel project since it dropped on June 27, 2026. It's a small patch release, but it fixes three things that were genuinely annoying in 4.3.2. Worth upgrading for the Authorize attribute fix alone.

What's Fixed

• Named error bags preserved — In 4.3.2, named error bags were sometimes cleared during component re-rendering. That's fixed here. If you use custom error bags per form, this one matters.
• #[Authorize] improvements — The Authorize attribute now resolves arguments correctly, including class names passed as the only parameter. No more weird authorization denials for perfectly valid permissions.
• Pagination validation — The page query parameter in SupportPagination is now properly validated, preventing edge cases where bogus page values could slip through.

Quick Upgrade Notes

Upgrading from 4.3.2 is a one-liner: composer require livewire/livewire:^4.3.3. No breaking changes, no config changes, no blade template edits. If you're coming from v3, read the v4 migration guide first — there's quite a bit that changed between major versions.

Why v4 Matters Now

Livewire 4 introduced single-file components, Island architecture for selective reactivity, and the Blaze templating engine. These aren't just buzzwords — in practice, Island mode cuts the JavaScript payload by roughly 40% on pages with mostly-static content. If you haven't moved to v4 yet, 4.3.3 is a stable release to target.

Bottom Line

Patch releases don't get headlines, but 4.3.3 cleans up real bugs that affected real projects. The Authorize fix alone saves you from adding workarounds to your middleware. Update now, move on.