Eloquence Laravel Package

Product Decisions This Supports

• Framework upgrade planning: This release (9.0.0) adds Laravel 9 support, which directly unblocks or de-risks a Laravel 9 migration. PMs can now schedule the framework upgrade without needing to replace or fork this dependency.
• Build vs. buy: Continued compatibility signals active maintenance. That strengthens the case for keeping this as a bought/community dependency rather than building equivalent functionality in-house.
• Roadmap sequencing: If Laravel 9 adoption is a platform initiative, this package's release is a prerequisite checkbox. Track it as a dependency milestone in the upgrade epic, not as a standalone feature.
• Risk and lifecycle management: A major version aligned with Laravel 9 implies the maintainers are tracking upstream support windows. Use this to justify staying on supported Laravel/PHP versions for security and compliance purposes.
• Use cases: Relevant wherever this package underpins user-facing functionality; the PM decision is primarily about upgrade timing, not new end-user capability. The release note does not indicate new product features.

When to Consider This Package

• Adopt when: Your application is on or moving to Laravel 9 and you need the package to remain compatible. Version 9.0.0 is the entry point for that upgrade.
• Adopt when: Active maintenance and upstream framework tracking are selection criteria — this release is evidence of both.
• Look elsewhere or defer when: You are on an older Laravel version and cannot yet upgrade; pin to the prior major and plan the jump. Also reassess if the package's own major-version cadence is coupled to Laravel's, since that means every framework upgrade becomes a coordinated dependency upgrade.
• Caveat: The available information is limited to a single release note. Before committing, confirm the actual breaking-change surface (config, namespaces, service providers, minimum PHP version) and validate with an engineering spike. Treat "major version" as a signal to review, not as proof of stability.

How to Pitch It (Stakeholders)

For executives: A maintenance release confirms the package now supports Laravel 9. It removes a blocker from our framework upgrade path, keeps us on a supported and secure platform, and avoids the cost of replacing the dependency with custom code. No new product features — this is platform hygiene and risk reduction.

For engineering: Version 9.0.0 adds Laravel 9 support. Plan the upgrade as part of the Laravel 9 migration, verify PHP version and dependency constraints, and run the test suite before rollout. Because this is a major version, confirm there are no undocumented breaking changes in configuration or integration points.