Skip to content

Filament v4.13.2 Released: Bug Fixes, UI Improvements, and Translation Updates

Filament v4.13.2 ships with targeted bug fixes for tables, the rich editor, repeatable entries, and tenant ownership, plus translation updates for German, Czech, Brazilian Portuguese, and Khmer.

Published · Updated · 3 min read

Filament v4.13.2 Released: Bug Fixes, UI Improvements, and Translation Updates

Filament v4.13.2 Is Out — Here's What Changed

Released on 15 September 2026 by @danharrin, Filament v4.13.2 is a focused patch release that addresses a handful of UI bugs, improves multi-tenancy behaviour, refines component internals, and broadens community translation coverage.

Bug Fixes

Tables

Two table-related fixes land in this release:

  • Mobile-stacked tables now preserve desktop spacing. Previously, switching to the stacked mobile layout could inadvertently drop spacing that was intentional on larger screens. PR #20490 restores that behaviour.
  • Session persistence is disabled for tables inside a TableSelect. Persisting table state inside a TableSelect caused unexpected filter and pagination bleed between uses. PR #20486 disables that persistence so each TableSelect starts clean.

Rich Editor

  • The rich editor content area is now fully clickable. Clicking anywhere in the editor region — not just on existing text — correctly focuses the editor and positions the cursor. (PR #20483)
  • Preloaded rich editor mentions are now filtered client-side. When mentions are preloaded, the filtering logic now runs in the browser rather than triggering unnecessary server round-trips. (PR #20501)

Repeatable Entries

Repeatable entry items are now rebuilt after in-place collection mutations. If the underlying collection was mutated directly (rather than replaced), the rendered items could fall out of sync. PR #20500 ensures the view always reflects the current state.

Multi-Tenancy

Tenant association is now skipped for HasOneThrough ownership relationships. Attempting to associate a tenant through a HasOneThrough relation would throw an error because that relation type does not support associate(). PR #20506 adds a guard so those relationships are handled gracefully.

Panel Routing

The panel root-route check now strips the URL scheme before comparing. This prevented a subtle bug where http:// and https:// variants of the same URL were treated as different routes. (PR #20488)

The page header content area no longer gets squeezed when many actions are present. A layout fix in PR #20491 ensures the title and description retain their space regardless of how many header actions are registered.

Search configuration is now defined directly on CheckboxList rather than being inherited indirectly. This is an internal refactor (PR #20481) that makes the component easier to reason about and extend.

Translation Updates

This release includes community-contributed translation improvements across four locales:

| Locale | Change | |---|---| | German (de) | Fixed is_filled summary string in the Query Builder | | Czech (cs) | General translation corrections | | Brazilian Portuguese (pt_BR) | Added missing strings for select actions | | Khmer (km) | Updated translations |

Documentation

  • App authentication cache requirements are now documented.
  • The shared Blueprint workflow and an Astra comparison are now covered in the docs.

Dependency Bumps

  • @tiptap/core bumped from 3.30.4 → 3.30.5
  • sharp bumped from 0.35.0 → 0.35.4 (docs-assets screenshots tooling)

Key Takeaways

  • Fix mobile-stacked table spacing regression.
  • Disable session persistence inside TableSelect to prevent state bleed.
  • Rich editor is now fully clickable and filters mentions client-side.
  • Repeatable entries rebuild correctly after in-place collection mutations.
  • HasOneThrough tenant ownership no longer throws on association.
  • Panel root-route check is now scheme-agnostic.
  • Four locale translation packs updated.

Source: Filament v4.13.2 on GitHub

Frequently asked questions

Why is session persistence disabled for tables inside a TableSelect in v4.13.2?

Persisting table state (filters, pagination, etc.) inside a TableSelect caused state to bleed between separate uses of the component. Disabling persistence ensures each TableSelect instance starts with a clean state.

What was the HasOneThrough tenancy bug fixed in v4.13.2?

Filament was attempting to call associate() on a HasOneThrough relationship when associating a tenant, which is not supported by that relation type. The fix adds a guard that skips tenant association for HasOneThrough relationships.

How does the repeatable entry fix in v4.13.2 affect my forms?

If you mutate a repeatable entry's underlying collection in place (rather than replacing it entirely), the rendered items will now correctly rebuild to reflect the updated collection state.

Mohamed Said

About the author

Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow.

About GitHub LinkedIn WhatsApp Email Address My CV

Have a technical challenge?

Tell me what you’re building. I reply within two working days.

Discuss your project