Product Decisions This Supports

Runtime modernization and technical debt reduction: v1.2.0 removes PHP 7.1 support, signaling the package now targets maintained PHP versions. This is a forcing function to review any remaining PHP 7.1 environments and prioritize upgrade work.
Build vs. buy / adoption timing: If our application still runs PHP 7.1, adopting v1.2.0 is blocked until the runtime is upgraded. That upgrade cost should be factored into any build-vs-buy or vendor-selection decision.
Roadmap sequencing: Teams on PHP 7.2+ can adopt v1.2.0 as a routine maintenance update. Teams on PHP 7.1 should either pin to the prior release or schedule the PHP upgrade before taking this version.
Risk and security posture: PHP 7.1 is end-of-life and no longer receives security fixes. Dropping support aligns the package with a safer baseline and reduces the risk of running unsupported infrastructure.
Use-case fit: The release does not add new product capabilities; its main product implication is a compatibility boundary. Confirm the package’s supported Laravel and PHP matrix before committing it to a roadmap.

When to Consider This Package

Consider adoption if: the application runs on a supported PHP version (PHP 7.2 or later, subject to confirming the package’s exact Composer constraints) and a compatible Laravel version; the team has a routine dependency-update process; and the package’s core functionality fits the product need.
Look elsewhere or defer if: the product is locked to PHP 7.1, has no near-term runtime upgrade path, or requires vendor support for end-of-life PHP versions.
Pin the previous release if: v1.2.0 is otherwise desirable but the runtime upgrade cannot happen immediately. Treat this as a temporary risk mitigation, not a long-term strategy.
Validate before committing: check the package’s full version support policy, Laravel compatibility, upgrade notes, and whether dropping PHP 7.1 is the only breaking change in v1.2.0.

For executives: This is a maintenance release that keeps the package aligned with supported PHP versions. It has no new feature value, but it reinforces that PHP 7.1 is no longer viable. If we are still on PHP 7.1, we should treat the runtime upgrade as a near-term priority because that version no longer receives security updates.
For engineering: v1.2.0 drops PHP 7.1 support. Verify Composer constraints and the CI matrix, confirm the supported Laravel versions, and decide whether to upgrade PHP, pin the prior package release, or defer adoption. This is a breaking change only for PHP 7.1 environments, but it should be captured in dependency and upgrade planning.