Cart Laravel Package

Product Decisions This Supports

• Framework upgrade sequencing. v2.0.0 is the release that makes this package viable on Laravel 13. If Laravel 13 is on the roadmap, this release is the gate that unblocks the dependency—it belongs in the upgrade plan, not after it.
• Platform floor / support matrix. The PHP 8.3+ requirement is a product-level constraint, not just a technical one. Adopting v2.0.0 means formally dropping PHP 8.2 across the estate; that decision affects hosting images, CI runners, and any shared libraries pinned to older runtimes.
• Build vs. buy. A package that ships on day-one of a new Laravel major with correct Testbench/Pest alignment is signaling active maintenance. That reduces the expected cost of "buy" (adopt + track) relative to building and owning the equivalent internally, where you would absorb the same upgrade work yourself.
• Upgrade cost estimation. The jump to Testbench v11 and Pest v4 alongside Laravel 13 support indicates a coordinated major-version bump. Treat v2.0.0 as a major upgrade with its own ticket, regression pass, and rollback plan—not a patch bump.
• Test infrastructure decisions. If our own test suite pins Pest v3 or an older Testbench, this release forces a parallel test-tooling upgrade in any project that consumes it, which is real scope to budget.
• Roadmap timing. "Supports Laravel 13" is a leading indicator that the ecosystem is converging on that major. It informs when it is safe to commit to Laravel 13 in our own release commitments.

When to Consider This Package

Consider adopting v2.0.0 when:

• The project is on, or is actively planning, Laravel 13.
• Runtime is PHP 8.3+, or the PHP upgrade is already funded and scheduled.
• The consuming project's test stack is on, or can move to, Pest v4 / Testbench v11. If it cannot, this release creates a conflict rather than resolving one.
• You need a dependency with demonstrated responsiveness to new Laravel majors—the fastest way to validate that is a maintainer who publishes a compatible release close to the framework launch.

Look elsewhere or defer when:

• The project is pinned to PHP 8.2 or earlier with no near-term upgrade path. v2.0.0 is not adoptable, and staying on v1.x is a deliberate (and time-boxed) decision that needs an owner and an expiry date.
• You are on Laravel 11/12 and not moving soon. Confirm whether v2.0.0 still carries backward support for your version—the release notes only state the forward edge, not the retained floor. If v2.0.0 drops older Laravel majors, you are choosing between an unwanted framework upgrade and a frozen dependency.
• Your test suite is deeply invested in Pest v3 and migrating it is not worth the package's value.
• Unverified: the release notes describe compatibility, not capability. They say nothing about new features, deprecations, or behavioral changes. Before committing, read the changelog diff between v1.x and v2.0.0 for anything beyond dependency bumps—major version numbers imply breaking changes, and none are documented here.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a maintenance-driven major release: it brings our Laravel integration in line with Laravel 13 and raises the minimum PHP version to 8.3. There is no new product capability in it. The decision it forces is a platform one—when we move to PHP 8.3 and Laravel 13. Adopting it keeps us on a supported, actively maintained dependency and avoids a future forced migration under time pressure. Deferring is acceptable but should be time-boxed, because the cost of the eventual upgrade only grows.

For engineering leads: v2.0.0 aligns with Laravel 13 and pins Testbench v11 / Pest v4, requiring PHP 8.3+. Treat it as a breaking major: plan a dedicated upgrade ticket covering the PHP runtime bump, the test-tooling migration (Pest v4 is a major in its own right), and a full regression pass. Confirm the retained support floor for Laravel 11/12 before we commit—the notes only describe the forward edge. Sequence it as an enabler for the Laravel 13 workstream, not as a follow-on to it, and land the PHP 8.3 upgrade first so the package bump is a one-line change.

Open questions to resolve before approval: the v1→v2 changelog diff beyond dependency versions; whether older Laravel majors remain supported; and whether any consuming project has a hard block on Pest v4.