Product Decisions This Supports

Roadmap/dependency planning: v3.3.0 confirms the package now targets Laravel 12+ and Pest 5; any roadmap item depending on it should be sequenced after the Laravel 12 upgrade.
Build vs buy: this is a compatibility/maintenance release, not a new feature release. Keep or adopt only if the package’s existing capability is worth the major-version migration cost.
Testing stack alignment: teams standardizing on Pest 5 can evaluate it without a known Pest compatibility blocker; teams on older Pest/PHPUnit should validate before adoption.
Upgrade risk management: v2.4.0 → v3.3.0 is a major-version boundary with dropped Laravel 10/11 support, so pinning and regression testing are required.
Use-case fit: suitable for Laravel 12/Pest 5 applications that need this package’s functionality; legacy Laravel 10/11 applications should defer or stay on v2.4.0.

When to Consider This Package

Consider it when the application is on Laravel 12+, the team uses or is moving to Pest 5, and the package’s functionality is already part of the product or planned scope.
Consider a planned upgrade if already using v2.x and the Laravel 12 migration is underway; treat v3.3.0 as a dependency modernization step.
Look elsewhere or defer if the application remains on Laravel 10/11, cannot upgrade Pest, needs long-term legacy support, or expects new product features from this release.
If adopting fresh, verify the package’s core capability against alternatives first; this release provides compatibility value, not differentiated product functionality.

Executive summary: v3.3.0 is a maintenance release that adds Pest 5 support and drops Laravel 10/11. It reduces the support matrix and aligns the package with the current Laravel/Pest stack, but delivers no new business features.
Engineering summary: this is a breaking change for Laravel 10/11 users. Upgrade only alongside a Laravel 12 migration; otherwise pin to v2.4.0. Budget regression testing and dependency constraint updates.
Recommendation: adopt or retain if already on Laravel 12 and Pest 5; defer if blocked on older Laravel versions. The value is maintainability and stack alignment, not new product capability.