Product Decisions This Supports

Fixes critical performance regression in v6.10.0 by resolving a bug where the datasource() method was incorrectly called twice for Collection-based datasources, improving reliability for high-frequency table operations (e.g., real-time dashboards or bulk actions).
Maintains backward compatibility with v6.10.0’s new lifecycle hooks (transformQuery, actions, rows) and SearchHandler, ensuring no disruption to teams leveraging advanced customization while fixing an edge case.
Reduces technical debt for Livewire admin panels by patching a subtle but impactful issue, particularly for applications relying on in-memory collections (e.g., caching layers, API-driven data).
Reinforces trust in the package for production use by addressing a regression introduced in the latest minor release, aligning with Laravel’s focus on stability.

When to Consider This Package

Use this package when:
- You’re using v6.10.0+ and rely on Collection datasources (e.g., for cached or API-fetched data) and noticed duplicated datasource() calls or inconsistent behavior.
- You need stable, high-performance tables for Livewire admin panels with minimal custom code but require hooks for advanced use cases (e.g., query transformations, dynamic actions).
- Your team prioritizes long-term maintenance and wants to avoid forking the package due to minor regressions.
Avoid if:
- You’re not using v6.10.0 (upgrade recommended, but this fix is v6.10.0-specific).
- Your tables exclusively use Eloquent models (this fix targets Collection datasources only).
- You need highly specialized features (e.g., WebSocket updates, hierarchical data) beyond PowerGrid’s scope.

For executives: "v6.10.1 patches a critical regression in v6.10.0 where table data sources were processed twice for collections—fixing potential performance hiccups in dashboards or bulk operations. This is a zero-risk upgrade that stabilizes our Livewire admin panels while keeping all the new customization hooks (like transformQuery) intact. No downtime, just reliability for our data-heavy tools."
For engineering: "v6.10.1 fixes a Collection datasource bug introduced in v6.10.0 where datasource() was called twice, causing subtle issues in high-traffic tables. This is a point release with no breaking changes—just a critical stability patch. If you’re using Collections (e.g., for API data or caching), upgrade to avoid redundant queries. Docs and hooks remain unchanged: changelog."