Laravel Redash Laravel Package

Product Decisions This Supports

• Build vs buy. A package shipping Laravel 12 and Pest 4 support on its 1.2.0 line is one that keeps pace with the framework's current major. That materially weakens the strongest argument for building in-house ("we'll end up forking it in six months anyway").
• Roadmap sequencing. If a Laravel 12 upgrade is on the roadmap, this dependency is not a blocker. It can ride along with the platform upgrade rather than being scheduled ahead of it.
• Upgrade-window planning. Pest 4 support implies the package's own suite runs on current test tooling, which means fewer internal test-harness exceptions and less bespoke CI work for us.
• Use cases. Standard-stack Laravel work — internal tooling, back-office/admin surfaces, integrations — where staying on supported framework versions is a security and compliance requirement rather than a preference.
• Engineering standards. Keeping a dependency that tracks current majors sets a reasonable maintenance bar for the rest of the dependency list.

When to Consider This Package

Adopt when:

• We are on, or moving to, Laravel 12 — 1.2.0 is the minimum version to pin.
• Our test suite is, or will be, on Pest 4 (1.2.0 avoids a version-conflict fork).
• We need the dependency to survive a framework major upgrade without an internal patch or paid fork.
• The surface area it covers is not core to our differentiation.

Look elsewhere or hold when:

• We are pinned to Laravel 10/11 for other reasons — confirm a maintained branch exists before assuming 1.2.0 helps.
• Its scope overlaps something we already own, or a first-party Laravel facility now covers it.
• We need an LTS-style support commitment. A compatibility bump shows the maintainer is active; it does not constitute a contractual guarantee.
• The open question is capability. 1.2.0 is a compatibility release and says nothing new about what the package can do. If we are still evaluating fit, this release does not resolve it.

How to Pitch It (Stakeholders)

For executives: This dependency is now current with the framework version we are standardizing on and with our test tooling. That removes a known upgrade blocker and lowers the probability of an unplanned fork or emergency migration later in the year. Adoption cost is low; the maintenance signal is good.

For engineering: 1.2.0 adds Laravel 12 and Pest 4 support. Treat it as the floor for new installs and review the full changelog before upgrading existing services. A major-version support bump is the most likely place for transitive dependency drift to surface even without API changes — re-run the suite and confirm our supported-version matrix. If we are still on Laravel 11, confirm which line to pin.

For the roadmap: pin 1.2.0, open a ticket to validate against Laravel 12 in staging, and re-review the dependency at the next platform upgrade. No roadmap change is required on the basis of this release alone.