Kanuu Laravel Laravel Package

Product Decisions This Supports

• Adoption/upgrade timing: v1.0.0 is a platform-compatibility milestone, not a feature release. It is suitable for products already targeting PHP 8.1 and Laravel 9, but it is a breaking change for applications still on PHP 7.4 or Laravel 7.
• Roadmap planning: If this package is a dependency in the product, treat Laravel 9 / PHP 8.1 readiness as a prerequisite for upgrade work and sequence it with the broader platform modernization roadmap.
• Build vs. buy: The v1.0.0 tag signals a stable release and explicit modern-framework support, which reduces dependency risk on modern stacks. For legacy stacks, the migration cost may justify deferring adoption, selecting an alternative, or building a narrow internal replacement if the package’s domain functionality is not strategic.
• Use-case fit: Consider it where the package’s functionality is needed and the product is on, or can move to, Laravel 9 / PHP 8.1. Do not position it as a solution for legacy Laravel 7 / PHP 7.4 applications.

When to Consider This Package

• Consider adoption when the application is on PHP 8.1+ and Laravel 9+, the package’s functionality maps to a real product need, and the team can validate compatibility through its own test suite.
• Consider it when dependency hygiene matters: v1.0.0 shows active maintenance against a modern Laravel/PHP baseline and provides a clear compatibility target.
• Look elsewhere or defer when the product is still on PHP 7.4 or Laravel 7, when upgrading the runtime/framework is not funded, or when the package is critical and no migration path is available.
• Before adopting, verify the package’s actual feature set, security posture, maintainer responsiveness, and test coverage beyond these release notes; the release notes establish compatibility signals, not product capability.

How to Pitch It (Stakeholders)

Executives: v1.0.0 is a stability and modern-platform support release. It is a good dependency choice only if our product roadmap is aligned to PHP 8.1 and Laravel 9. For legacy applications, this is a breaking change that should be budgeted as migration work, not treated as a drop-in upgrade.

Engineering: Plan the upgrade around PHP 8.1 / Laravel 9, add those versions to CI, and explicitly remove PHP 7.4 / Laravel 7 from the support matrix. Treat v1.0.0 as the supported baseline going forward and validate integration behavior before rollout.

Product: This release supports dependency modernization and reduces the risk of relying on an unmaintained package on newer Laravel versions. It does not, by itself, add user-facing features; value comes from enabling the product to stay on a supported framework baseline.