Laravel Thermite Laravel Package

Product Decisions This Supports

• Upgrade/roadmap gating: 1.0.0 adds Laravel 9 support, so this package can unblock or justify a Laravel 9/PHP 8+ upgrade for dependent applications.
• Build vs. buy: If the package’s capability matches a product need, adopting a maintained package is likely cheaper than building and maintaining equivalent in-house Laravel integration.
• Platform standards: Dropping PHP 7.3/7.4 and Laravel 7.x means this is a breaking compatibility release; product planning should account for migration effort, CI updates, and dependency constraints.
• Risk management: The release signals active maintenance and a stable 1.0 major line, but teams must verify that their Laravel/PHP versions are supported before adopting or upgrading.
• Use cases: Best suited to Laravel 9-compatible applications on modern PHP that need the package’s specific functionality and can absorb a major-version dependency bump.

When to Consider This Package

• Consider it when the application is on Laravel 9 (or an upgrade is already planned) and PHP 8+, and the package’s capability is on the roadmap.
• Consider it when the team wants a maintained integration rather than custom Laravel/PHP code, and can follow major-version upgrades.
• Look elsewhere or defer if the application is still on PHP 7.3/7.4 or Laravel 7.x, since this release explicitly drops those versions.
• Avoid adoption if the team cannot upgrade soon, needs long-term support for older Laravel versions, or the package’s functionality is not differentiated enough to justify another dependency.

How to Pitch It (Stakeholders)

• For executives: 1.0.0 is primarily a compatibility and maturity milestone: it supports Laravel 9 and modern PHP, which can reduce custom maintenance and align the product with supported framework versions. It is also a breaking release for older stacks, so adoption should be tied to an upgrade plan.
• For engineering: Treat this as a dependency upgrade, not a feature release. Validate Composer constraints, run CI against PHP 8+/Laravel 9, and plan migration for any apps still on PHP 7.3/7.4 or Laravel 7.x.