Laravel Companion Apps Laravel Package

Product Decisions This Supports

• Platform upgrade sequencing. This release is about framework currency, not features: the package now declares Laravel 13 support. For a PM, the value is that Laravel 13 migration work can be planned through this dependency instead of routed around it. If the upgrade was previously blocked or deferred because of this package, that gate is now open.
• Roadmap dependencies. Anyone sequencing a Laravel 13 upgrade in a quarter should list this package's 2.2.0 release as a prerequisite, not an afterthought. This is a planning input, not a feature input.
• Build vs. buy weighting. Shipping support for a new Laravel major shortly after that major lands is a concrete maintenance-health signal. It lowers the carrying cost and abandonment risk you'd otherwise price into a "build" argument.
• Dependency pinning policy. Moving off a version pin and onto the current major is a decision this release enables. The practical question is whether your own composer.json constraints can now widen for this package.
• What it does not support. There are no functional additions, deprecations, or behavior changes here. Do not read it as a signal about product direction, performance work, or API stability beyond the Laravel 13 constraint. Scope claims about the package's own feature surface should not be derived from this changelog.

When to Consider This Package

Consider adoption when:

• You are on Laravel 13, or you have a committed plan to get there within the dependency's support window.
• You want your dependency set to have no outstanding major-framework gaps, so upgrade work is one coordinated motion rather than a series of exemptions.
• The package's own purpose already fits a need you have — this release speaks only to compatibility, so it should be a tiebreaker between otherwise comparable options, not the deciding factor.

Look elsewhere when:

• You are staying on an older Laravel line for a while and this release offers you nothing; assess the previous minor instead.
• You need evidence of a stated support/deprecation policy (how many Laravel majors are maintained concurrently, how far ahead support is announced). A single compatibility bump confirms responsiveness once; it does not establish a pattern.
• Your decision hinges on the package's functional capability. Nothing in 2.2.0 helps you evaluate that, so escalate to engineering evaluation or look for packages with a clearer feature roadmap.
• Version cadence matters to you. A minor bump (2.2.0) for framework support is a reasonable convention, but if your policy expects compatibility work in patch releases, note the divergence and confirm the maintainer's versioning intent before relying on it.

Assessment confidence caveat: this review is based on the 2.2.0 release notes alone (a single "Laravel 13 support" addition) with no prior assessment on file. Treat every statement above as being about compatibility and maintenance posture only — the package's functional assessment is still outstanding.

How to Pitch It (Stakeholders)

For executives: This is a routine, low-risk maintenance release — non-breaking, minor version, no behavior changes. Its strategic value is narrow but real: it removes this dependency as a blocker to the Laravel 13 upgrade, which is the kind of thing that otherwise surfaces late in a platform project as an unplanned workaround. No budget ask, no migration risk, no customer-facing impact.

For engineering: 2.2.0 adds Laravel 13 support only — no new APIs, no deprecations, no changed defaults. Safe to pick up within the 2.x line. The action is to widen the framework constraint and confirm the existing test suite runs clean on Laravel 13. If you're mid-cycle on the upgrade, this package can be included in the same wave rather than sequenced separately.

For the portfolio/dependency review: Treat this as one data point on maintenance health — maintainers are tracking upstream majors. Before relying on it in a long-lived product, ask for the support policy: which Laravel versions are supported simultaneously, and how much notice is given before an older major is dropped. That commitment, not this release, is what determines whether the dependency is safe for the next three years.