Repository navigation
13.2.0 — Rich details, refined UI and localized dates
This minor release completes the K1–K5 implementation review on top of the existing optional Eloquent and multi-source board integration.
Highlights
- Optional
CardDetailsProvider,CardDetailSectionDataandCardDetailActioncontracts for lazy, permission-scoped detail sections; the base DataProvider interface is unchanged. - Bounded section paging, escaped text, sanitized links, trusted custom templates, independent section permissions and stable operation identities for domain-owned retry handling.
- Configurable drawer width, shared Board/List detail behavior, fixed header/footer, full-screen mobile layout, keyboard focus containment and background scroll locking.
- Improved toolbar, filters, cards/list rows, attachment covers, comments/checklists, member overflow and stage capacity display.
- Jalali dates with
morilog/jalali, optional locale/timezone/Persian digits, and Workbench-wide theme/locale controls. - Server-enforced CRM note transitions, optional archived-card deletion and configurable host create/edit page URLs.
Compatibility
PHP 8.3+, Laravel 13 and Livewire 4 remain supported. Existing providers and handlers do not need new mandatory methods. No commercial model or package migration is added. Host applications retain ownership of authorization, persistence, section actions, transactions and domain idempotency.
Run Composer update and rebuild or republish assets. Review published Blade overrides and the new date settings. The host demo loads Google fonts; the package itself inherits the host font. See upgrade notes and Drawer integration.
Local verification
- 264 PHP tests and 998 assertions passed.
- 21 Edge browser tests passed, including Reverb, multi-board/user isolation, touch, keyboard, RTL, themes and mobile.
- All 50 enterprise scenario reports were regenerated from executed test results.
- Composer validation, asset build and diff whitespace checks passed.
- A 100-card eager-loaded page used 3 queries; the 100k-row/10-column benchmark used 21 queries and hydrated 260 records for 250 visible cards.
Evidence and environment limits: implementation report, machine-readable results, and screenshots. Local verification used Windows, SQLite and Edge; other database/browser environments are reported by CI separately.