Product Decisions This Supports

Compatibility gating: Release 2.2.0 appears to raise the package’s minimum supported PHP version to 8.1. This supports a go/no-go decision on adoption or upgrade based on the application’s current PHP baseline.
Roadmap sequencing: Treat this as an infrastructure prerequisite rather than a feature release. If the product is not yet on PHP 8.1+, platform upgrade work should precede package upgrade work.
Dependency policy: Use this as a prompt to standardize the supported PHP baseline across the Laravel stack and identify other dependencies that already require PHP 8.1+.
Risk and rollback planning: If production remains on PHP 8.0 or earlier, defer 2.2.0 and pin to the prior package version until the runtime upgrade is complete.
Build vs buy: This release does not signal new product capability, so it should not change build-vs-buy on its own; it is a maintenance/compatibility data point.

When to Consider This Package

Consider it if your Laravel application is already on PHP 8.1+ and the package’s existing capabilities fit the use case.
Consider it as part of a broader PHP 8.1+ migration if the package is otherwise a good fit and the platform upgrade can be sequenced first.
Defer or look elsewhere if you are on PHP 8.0 or earlier and cannot upgrade soon; 2.2.0 introduces a hard compatibility gate.
Look elsewhere if you need evidence of feature velocity, bug fixes, or security maintenance; a one-line PHP-version change provides limited maintenance signal.
Evaluate alternatives if your organization requires documented breaking-change and migration notes; this release does not provide them.

Executives: “The new release is a platform-compatibility update, not a feature release. It requires PHP 8.1+, so adoption is tied to our PHP upgrade timeline. This release alone does not unlock new product value.”
Engineering: “Treat 2.2.0 as a breaking minimum-version bump. Confirm the runtime PHP version, check transitive dependencies, and decide whether to upgrade the platform or pin to the prior package version.”
Product/roadmap: “Do not position this as a customer-facing enhancement. Use it as a forcing function to verify our supported PHP baseline and sequence dependency upgrades deliberately.”