Smspilot Notifications Laravel Laravel Package

Product Decisions This Supports

• Framework-version roadmap. The package now tracks Laravel's major cadence through 13.x, so it can be counted on for the next upgrade cycle instead of being flagged for replacement. That removes a line item from the "dependencies at risk" list.
• Build vs. buy. Active upstream maintenance of compatibility is the main thing we'd otherwise pay for by forking or writing in-house. This release strengthens the buy side of that argument.
• Upgrade sequencing. Raising the minimum to Laravel ^11.0 is a hard install gate. Any surface still on Laravel 10 or earlier must either move the framework or pin this package to the previous minor — a roadmap dependency, not a code detail.
• Supported-environment statement. The ^11.0 floor plus the dev-container toolchain changes give us concrete inputs for the support matrix we publish to customers and to support/QA.

When to Consider This Package

Consider it when:

• The product runs on Laravel 11, 12, or 13, or will within the current planning horizon.
• You want a dependency whose maintainer is demonstrably keeping pace — this release shows both forward support (13.x) and routine hygiene (dev dependencies, container toolchain).
• You are consolidating onto fewer well-maintained packages rather than carrying custom equivalents.

Look elsewhere or defer when:

• Any part of the product is pinned to Laravel 10 or below and cannot move. v2.8.0 will not install there; adopting it means adopting an upgrade you cannot yet perform.
• Your release cadence is slower than the maintainer's. The prompt ^11.0 floor signals that old majors are dropped quickly — healthy for security, but it forces your upgrade timeline to match theirs.
• The release notes are your only signal. They describe compatibility and tooling, not functional capability. Confirm the package's actual feature set, licence, and maintainer responsiveness before committing.

How to Pitch It (Stakeholders)

Executives. This is a maintenance release whose headline is that the package keeps pace with Laravel: it adds Laravel 13 support and formally drops Laravel 10 and older. The practical consequence is a scheduling item, not a risk — it sets a floor on which platform versions we can run, and it tells us the vendor intends to stay current. Low cost, low risk, contingent on our own Laravel upgrade timeline.

Engineering. v2.8.0 adds Laravel 13.x support and raises the minimum supported Laravel to ^11.0. Treat that as breaking below 11 — bump the Composer constraint alongside the framework upgrade, not ahead of it. The Docker image moves to PHP 8.5 and Composer 2.10; those should be CI-only, but verify the published PHP requirement before assuming the runtime floor moved. Dev-dependency updates are routine. Recommended action: upgrade inside the next framework-version window and pin to the prior minor until then.