Product Decisions This Supports
- Upgrade timing and platform baseline: 3.0.0 is a compatibility/maintenance release, not a feature release. It sets a clear support floor at Laravel 5.6 and PHP 7.1.3. This supports a decision to schedule the upgrade alongside broader Laravel/PHP modernization rather than as a standalone roadmap item.
- Build vs. buy / dependency retention: The package is now explicitly aligned with Laravel-supported minimums. If your product is already on Laravel 5.6+ and PHP 7.1.3+, this release reduces the “abandoned or lagging dependency” risk. If you are pinned below those versions, this release forces a fork, delayed upgrade, or replacement decision.
- Technical debt and compliance planning: Strict typing is a code-quality and maintainability signal. It supports decisions to standardize on typed PHP code, tighten static analysis/CI, and reduce long-term maintenance cost—without promising new user-facing capability.
- Release and QA scope: Because there are no new features or deprecations, PM can treat this as a low-product-risk but non-zero-engineering-risk release. Allocate QA to integration/regression testing, especially around mocked or subclassed package behavior, rather than user acceptance testing for new functionality.
- Support policy communication: The major version bump is a useful forcing function to document supported Laravel/PHP versions for internal stakeholders and downstream consumers of your own product.
When to Consider This Package
Consider adopting or upgrading to 3.0.0 when:
- Your application already runs Laravel 5.6 or newer and PHP 7.1.3 or newer. The package’s support floor now matches Laravel’s own minimum, which simplifies compatibility conversations.
- You want a dependency that is actively maintained against supported framework baselines and is willing to make explicit major-version breaks rather than silently dropping older platforms.
- You value code-level maintainability signals such as strict typing, which can improve static analysis, reduce implicit type coercion bugs, and make integration behavior more predictable.
- You are planning a broader platform upgrade and want dependencies that will not block Laravel/PHP modernization.
- You can absorb a major-version upgrade with normal regression testing. Strict typing can surface latent type errors in how your code calls or extends the package, so treat it as a compatibility review item.
Look elsewhere or defer when:
- You are locked to Laravel below 5.6 or PHP below 7.1.3. This release is explicitly not for you; you would need to stay on the prior major line, fork, or replace the package.
- You require new product capabilities from this release. 3.0.0 contains no new features and no deprecations; its value is platform alignment and code quality, not functional expansion.
- You cannot tolerate any major-version change in the current planning cycle, even one that is primarily a support-baseline and typing change.
- You need a vendor with a long-term support commitment beyond what the release notes state. The notes define minimum versions, not a formal LTS policy.
How to Pitch It (Stakeholders)
Executive summary: Version 3.0.0 is a maintenance-focused major release. It raises the minimum supported platform to Laravel 5.6 and PHP 7.1.3 and updates the codebase to strict typing. There are no new features and no deprecations. The business value is reduced dependency risk and improved code maintainability, not new product functionality.
For engineering: Plan this as a compatibility upgrade. Confirm your Laravel/PHP versions meet the new floor, run the full regression suite, and pay particular attention to strict-typing-related failures in integrations, mocks, subclasses, and any code passing loosely typed values into the package. Because this is a major version, pin deliberately and document the upgrade in your dependency changelog.
For product/roadmap: This release does not add roadmap capability. It supports a “keep dependencies current” hygiene initiative and should be bundled with platform modernization work rather than presented as a feature delivery. If any part of the estate remains on Laravel below 5.6 or PHP below 7.1.3, flag that as a separate modernization risk and decide explicitly between upgrade, fork, or replacement.