Laravel Perpage Resolver Laravel Package

Product Decisions This Supports

• Upgrade sequencing: 2.0.0 is a hard compatibility gate. It is explicitly backwards-incompatible and supports only PHP 8.0 and Laravel ^8/^9. This directly informs whether to schedule the upgrade, defer it, fork the package, or replace it.
• Security prioritization: The illuminate/database dependency was raised to ^8 “due to security reason.” For products on Laravel 8/9, this supports treating the upgrade as a security/compliance item rather than a feature investment.
• Build vs. buy / maintenance risk: A major release that pins to PHP 8.0 only and Laravel 8/9 only — with no stated feature additions — signals a narrow support window and likely maintenance lag. This supports evaluating alternatives, vendoring, or forking if the package is on a critical path.
• Roadmap constraint: If the product roadmap includes PHP 8.1+ or Laravel 10+, this package becomes a blocker. Decide now whether to delay the framework upgrade, isolate the dependency, or replace it.
• No product-facing value to plan around: The release is compatibility and security maintenance. It should be handled through technical debt and security planning, not positioned as a feature release.

When to Consider This Package

• Consider adoption only when the application is on PHP 8.0 and Laravel 8.x or 9.x, and the package’s functionality is genuinely needed.
• Strong case for upgrading if you are on an older illuminate/database version and need the referenced security fix.
• Look elsewhere or plan a fork/replacement if:
  • You are on PHP 8.1+ — the release notes state PHP 8.0 is the only supported version.
  • You are on Laravel 10+ or planning to move there soon.
  • You need predictable long-term support and upgrade cadence; the narrow support matrix suggests limited forward maintenance.
  • You cannot absorb the backwards-incompatible changes across the 1.x → 2.x boundary.
• Treat a fork as viable if the package’s functionality is valuable but its compatibility window is already behind current PHP/Laravel releases.

How to Pitch It (Stakeholders)

For executives: This is a security-driven maintenance release, not a feature release. It addresses a security concern in the underlying database library but forces a breaking major-version upgrade and restricts the product to PHP 8.0 with Laravel 8/9. Recommendation: upgrade only if we are on that stack and exposed to the vulnerability; otherwise assess replacing or forking the package, because its supported platform now lags current PHP and Laravel releases.

For engineering: Version 2.0.0 is backwards-incompatible, supports only PHP 8.0 and Laravel ^8/^9, and bumps illuminate/database to ^8 for security. Plan migration testing, audit all package usages for breaking changes, and confirm dependency conflicts before upgrading. Flag that the PHP 8.0-only support will block later PHP 8.1+ upgrades and should be tracked as a dependency risk.