Events Log Laravel Laravel Package

Product Decisions This Supports

• Upgrade sequencing for the platform: This release confirms the package tracks Laravel's release cadence closely (13.x support lands alongside the framework). That makes it a safe dependency to keep in the "upgrade with the framework" bucket rather than a blocker you have to work around.
• Minimum-version policy: The floor is now Laravel ^11.0. If any product surface still runs Laravel 10 or earlier, this package can no longer be upgraded there — that is a roadmap forcing function, not a library detail. Decide whether to pin the old version or schedule the framework upgrade.
• Build vs. buy: Sustained maintenance (framework bumps, dev dependency refreshes, PHP 8.5 in CI) is evidence against rebuilding this capability in-house; the vendor/community is absorbing the compatibility tax you would otherwise own.
• Use cases: Best suited to products on a modern, supported Laravel baseline where the team wants dependencies that follow the framework rather than lag it. Treat it as infrastructure — it enables features, it doesn't define them.
• Deprecation hygiene: Dropping Laravel 10 and below is a signal the maintainers are willing to cut old versions. Budget for recurring major-version upgrades rather than assuming indefinite backward compatibility.

When to Consider This Package

Adopt when:

• Your application is on Laravel 11, 12, or 13 — the currently supported window.
• You want a dependency whose maintainers are actively tracking framework releases (this v3.7.0 shipped Laravel 13 support at or near the framework's release).
• Your team can absorb a periodic major-version upgrade; the project has demonstrated it will raise minimum versions.
• You are standardizing on modern PHP (CI is already validating against PHP 8.5).

Look elsewhere or hold off when:

• You are still on Laravel 10 or earlier. This release is a hard break for you; you would need to stay on the previous package major/minor and accept that you are now off the supported path.
• You need long-term support guarantees across multiple Laravel majors — this project's pattern is to move forward, not to maintain a wide compatibility matrix.
• Your runtime is pinned to an older PHP version and you cannot follow the PHP floor upward.
• The capability is peripheral to your product and you would rather not take on another upgrade obligation.

How to Pitch It (Stakeholders)

To executives: This is routine maintenance from a healthy dependency — it adds support for the newest Laravel version and officially ends support for Laravel 10 and older. The practical consequence is a planning item, not an incident: any product still on Laravel 10 or below needs a decision (upgrade the framework, or freeze this package at its current version). Everything already on Laravel 11+ is unaffected and gains forward compatibility with Laravel 13. Continued investment here is cheaper than replacing the capability ourselves.

To engineering: v3.7.0 raises the minimum Laravel version to ^11.0 and adds Laravel 13.x support; CI now runs Composer 2.10 and PHP 8.5. Treat this as a breaking change for anyone on Laravel ≤10 — audit composer.json constraints across services before rolling it out. For Laravel 11/12 codebases this should be a low-risk minor bump, but verify the PHP floor against your deployment images and confirm no transitive dependency conflicts. Add a recurring line item for this package's major upgrades; the maintainers have shown they will drop old framework versions on a regular cadence.