Php Paginator Laravel Package

Product Decisions This Supports

• Framework upgrade sequencing (Illuminate 12 → 13). This is a compatibility release, not a feature release. Its product value is that it unblocks a Laravel 13 migration: the package will not install alongside Illuminate 12 any more, so it becomes a hard gate in the upgrade plan rather than an optional follow-up.
• Dependency pinning and release-line policy. Because illuminate/http and illuminate/support moved to ^13.0, the package now maintains two parallel lines: ^3.3 for Illuminate 13 and ^3.2 for Illuminate 12. The PM decision is which line each product/service pins to, and for how long the 3.2 line is considered supported.
• Support matrix commitments. PHP floor stays ^8.3 while testing now covers PHP 8.5. Useful input for deciding whether to standardise runtime versions across services, and for stating a supported platform matrix in internal docs.
• Support-window expectations for roadmap planning. The maintainer's willingness to drop Illuminate 12 in a minor version (3.3.0, not 4.0.0) signals an aggressive framework-tracking cadence. Plan future upgrades as routine work each Laravel cycle, not as one-off projects.
• Build vs. buy / fork calculus. If any product is pinned to Illuminate 12 beyond this cycle, the option set is: stay on ^3.2 until upstream support ends, maintain a fork with widened constraints, or replace the dependency. This release makes that choice explicit and time-boxed.

When to Consider This Package

Consider adopting or upgrading to ^3.3.0 when:

• The consuming application is on, or is actively migrating to, Illuminate 13 — 3.3.0 is the only line that will resolve.
• You are already running the package on ^3.2 and want to stay on a line that continues to receive maintenance.
• You want a dependency whose release cadence tracks Laravel majors closely, reducing the lag between framework upgrades and package availability.

Look elsewhere, or defer, when:

• You are on Illuminate 12. Do not attempt 3.3.0; stay on ^3.2. Confirm with the maintainer how long ^3.2 will receive fixes, since this release demonstrates that minor versions can raise framework requirements.
• You have a long-lived LTS-style platform and need dependencies with stable, wide version constraints across multiple Laravel majors. The minor-version constraint bump is a poor fit for change-averse environments.
• You run PHP below 8.3 — unchanged in this release, but the floor is real and blocks adoption regardless of the Laravel version.
• You are evaluating the package for the first time. The release notes describe only compatibility changes; there is no functional evidence here to support a capability-based evaluation. Assess functionality separately before adopting.

How to Pitch It (Stakeholders)

To executives: This release contains no new features and no user-facing change. It is a maintenance update that keeps the package usable on the newest Laravel version. The practical consequence is a scheduled, low-risk engineering task: applications moving to Laravel 13 must move to this package version at the same time, and applications staying on Laravel 12 must not. There is no cost or revenue impact; the decision is purely about timing the upgrade and not letting it slip.

To engineering: Treat 3.3.0 as a breaking change in practice despite the minor version number. illuminate/http and illuminate/support now require ^13.0, so Composer will refuse to install this alongside Illuminate 12 — the dependency graph enforces the upgrade rather than warning about it. Coordinate the package bump with the framework bump in the same change; do not let them drift. PHP floor is unchanged at ^8.3, with the maintainer now testing on PHP 8.5, so runtime parity with the Laravel 13 target is the thing to verify in CI. If any service must remain on Illuminate 12, pin it explicitly to ^3.2 and record an owner and a deadline for revisiting, because the minor-version constraint bump shows the maintainer is willing to narrow compatibility without a major release.