Product Decisions This Supports

Roadmap: Confirms the package is tracking the latest Laravel release (13), so it can be part of a forward-looking upgrade plan if your application is on Laravel 10+. It does not support Laravel 9 or PHP 8.0–8.1, so any roadmap that includes those versions must account for a fork, delay, or replacement.
Build vs. buy: If you are on an older stack, 4.0.0 turns this into a migration cost. Evaluate whether to upgrade your app first, pin to an older package version, or switch to an alternative that still supports your Laravel/PHP versions.
Technical debt: Dropping old framework and PHP versions reduces the package’s maintenance and security surface. This supports a policy of keeping dependencies on supported runtimes, but it also forces you to retire legacy environments.
Use cases: No new functional features are introduced in 4.0.0. The release is a compatibility update only; existing use cases remain valid only for apps on Laravel 10–13 and PHP 8.2+ (confirm exact minimum in the package’s composer constraints).

When to Consider This Package

Adopt if your application runs Laravel 10, 11, 12, or 13 and PHP 8.2 or higher (PHP 8.0–8.1 support was removed; verify the exact minimum PHP version in the package metadata).
Consider it if you value a package that actively tracks new Laravel releases and is willing to drop old versions to stay current.
Look elsewhere if you are locked to Laravel 9 or PHP 8.0–8.1, or if you need a dependency with a slower, more conservative upgrade cadence.
Also reassess if the package’s core functionality is critical and you cannot coordinate a framework/PHP upgrade alongside this major version bump.

Executives: This release keeps the package aligned with the latest Laravel and PHP versions, reducing long-term security and maintenance risk. It is a breaking change for older stacks, so budget for a coordinated Laravel/PHP upgrade if you are not already on Laravel 10+ and PHP 8.2+.
Engineering: Version 4.0.0 adds Laravel 13 support and removes Laravel 9 and PHP 8.0–8.1. Treat it as a breaking change: upgrade your application’s Laravel and PHP versions before bumping this dependency. No new product features are included; the focus is runtime compatibility.