Filament Hidden Action Laravel Package

Product Decisions This Supports

• Upgrade sequencing and roadmap alignment: Release 1.0.3 is a compatibility/dependency release, not a feature release. It should inform when the product can adopt or update the package relative to the Filament 4.8+ upgrade.
• Build vs. buy / package adoption: The package is only a sensible “buy” if the product is already on Filament ^4.8 and the package’s functionality removes meaningful custom Filament work. The new minimum version is an adoption cost, not a standalone reason to adopt.
• Release risk management: The breaking change raises the minimum Filament version to ^4.8 and requires filament/actions: ^4.8 because Page::routes() now receives a PageConfiguration parameter. PM should plan coordination with engineering for dependency upgrades and regression testing around route registration/action behavior.
• Version pinning and support policy: If the product supports multiple Laravel/Filament versions, this release may create a compatibility split. PM should decide whether to maintain older package versions for Filament <=4.7 users or require an ecosystem upgrade.

When to Consider This Package

• Consider it when the product is already on Filament 4.8+, the package’s use case is validated, and the team can absorb the dependency upgrade and testing effort.
• Consider it during a planned Filament upgrade if the package’s functionality is valuable enough to justify aligning the application’s Filament version.
• Look elsewhere or defer if the product is locked to Filament <=4.7, has no near-term Filament upgrade path, or the package’s functionality is marginal relative to the upgrade cost.
• Do not adopt solely because of 1.0.3: this release contains no stated new feature value; it is primarily a compatibility floor change. Evaluate the package on its core functionality and total cost of ownership.

How to Pitch It (Stakeholders)

This release is a maintenance/compatibility update. It does not add new product capabilities, but it introduces a breaking dependency requirement: the package now needs Filament ^4.8 and filament/actions: ^4.8. For executives, frame it as a dependency-alignment decision: adopt or update only if the product is already moving to Filament 4.8+ and the package has a clear use case. For engineering, highlight the need to coordinate Composer upgrades, verify Page::routes()/PageConfiguration compatibility, and regression-test Filament actions and page routing. Recommendation: do not treat 1.0.3 as a reason to adopt from scratch; treat it as an upgrade gate for teams already committed to the Filament 4.8+ ecosystem.