Product Decisions This Supports

Laravel 10 readiness: Supports roadmap decisions to keep the product on a currently supported Laravel major and avoid end-of-life framework risk.
PHP baseline modernization: Dropping PHP 8.0 support signals the package now expects PHP 8.1+; use this as a forcing function to audit runtime images, CI matrices, and dependency compatibility.
Developer tooling standardization: Replacing PHP CS Fixer with Pint aligns style enforcement with Laravel’s default tooling, reducing custom CI configuration and onboarding friction.
Upgrade planning: Treat 7.0.0 as a breaking release for PHP 8.0 environments; schedule upgrade work rather than assuming a drop-in dependency update.
Build vs. buy / adoption: If the team needs Laravel 10-compatible tooling and is standardizing on Pint, this release improves fit; if PHP 8.0 must remain supported, defer adoption.

When to Consider This Package

Consider it when the product is on Laravel 10.x or planning that upgrade and the package’s role is compatible with the team’s PHP 8.1+ baseline.
Consider it when the team wants Pint-based style checking and is willing to retire PHP CS Fixer from CI.
Consider it when dependency freshness and maintained Laravel compatibility are more important than supporting older PHP runtimes.
Look elsewhere or delay when PHP 8.0 support is a hard requirement, when PHP CS Fixer is still required by existing pipelines, or when the package’s core functionality is unknown or not validated beyond release metadata.
Require engineering validation before adoption: confirm the package’s actual feature set, test coverage, issue activity, and upgrade path from the prior major.

Executives: Release 7.0.0 keeps the package aligned with Laravel 10 and modern PHP, reducing framework-obsolescence risk. The trade-off is a planned upgrade away from PHP 8.0, not an immediate product change.
Engineering: This is a breaking upgrade for PHP 8.0 environments. Update CI images, dependency constraints, and style tooling from PHP CS Fixer to Pint; validate Laravel 10 compatibility before merging.
Product/PM: Use this release to schedule a small platform-maintenance window, confirm no customer-facing behavior changes are expected, and track PHP 8.1+ adoption as a dependency-health milestone.