Product Decisions This Supports

Platform upgrade timing: v3.2.0 adds Laravel 13 and Statamic v6 support, which directly informs when the product can safely upgrade its CMS/framework stack without forking or replacing the search layer.
Build vs. buy for search: The package continues to track upstream framework releases, strengthening the case for buying/maintaining this dependency instead of building a custom search integration.
Roadmap dependency risk: Active compatibility releases reduce the risk of the search feature becoming a blocker for broader platform modernization work.
Use cases: Site search, content discovery, and query-based search within Statamic/Laravel applications. The Search component type declaration is a minor code-quality improvement, not a user-facing feature.

When to Consider This Package

Consider it when the product runs on Laravel and Statamic and needs a maintained, framework-aligned search component rather than a bespoke integration.
Consider it when upcoming roadmap work includes Laravel 13 or Statamic v6 upgrades and search must remain supported.
Look elsewhere if search requirements include advanced relevance tuning, large-scale faceting, or enterprise search operations better served by dedicated platforms (e.g., Algolia, Elasticsearch, Meilisearch) with their own Laravel integrations.
Look elsewhere if the product is not on Statamic, since the release notes are primarily Statamic- and Laravel-version compatibility signals.

Executive summary: This is a low-risk, maintenance-focused release. It confirms the search package is actively maintained and compatible with the newest Laravel and Statamic versions, reducing upgrade risk and avoiding custom search maintenance.
Engineering summary: v3.2.0 is a compatibility release: Statamic v6 support, Laravel 13 support, and a minor type declaration in the Search component. No breaking changes or deprecations are indicated. It is safe to adopt as part of planned platform upgrades, with normal regression testing around search behavior.