Laravel Zero Self Update Laravel Package

Product Decisions This Supports

• Platform lifecycle / upgrade planning: This release widens illuminate/console and laravel-zero/framework constraints to support Laravel Zero 13, directly unblocking a planned migration of CLI tooling to the current Laravel Zero major. It supports sequencing that upgrade rather than deferring it.
• Build vs. buy / dependency strategy: Confirms the package tracks upstream Laravel Zero releases instead of pinning teams to an older framework. Where we would otherwise fork or patch console constraints internally, adopting this package is the lower-maintenance path.
• Roadmap confidence: A compatibility-only release signals active maintenance and responsiveness to ecosystem changes. It is a positive input when deciding whether to keep this dependency on the roadmap for internal CLI apps, operational tooling, and PHAR-distributed commands.
• Risk management: Supports the decision to stay on supported Laravel Zero versions, reducing exposure to end-of-life framework constraints and Composer resolution conflicts.
• Scope note: No new features or API changes are introduced. This is a maintenance/compatibility release; it should not by itself drive new feature investment or change product scope.

When to Consider This Package

Consider it when:

• You are building or maintaining CLI applications on Laravel Zero and need a dependency that is compatible with Laravel Zero 13 and current illuminate/console versions.
• You have hit, or expect to hit, Composer constraint conflicts when upgrading Laravel Zero, and want a dependency that has already widened its constraints.
• You value a dependency that follows upstream framework majors promptly and requires little internal patching.
• You are standardizing internal tooling on Laravel conventions and want to avoid maintaining a private fork solely for version constraints.

Look elsewhere or defer when:

• Your applications are pinned to an older Laravel Zero major and cannot yet upgrade; compatibility with 13 does not help that path.
• You need functionality beyond what the package provides; this release adds no features, so unmet capability requirements remain unmet.
• The package duplicates a small amount of code you could own directly, and adding a dependency creates more upgrade overhead than it removes.
• You require a formal support/LTS commitment or an SLA that a community package does not provide.
• You cannot verify test/CI coverage across the newly supported framework version.

How to Pitch It (Stakeholders)

For executives: This is a low-risk maintenance release. It adds compatibility with Laravel Zero 13, keeps our CLI tooling on a currently supported framework, and reduces the cost and friction of the next upgrade. There are no new features, no breaking changes, and no new operational cost. The main value is avoiding upgrade blockers and end-of-life exposure.

For engineering: The package has widened its illuminate/console and laravel-zero/framework constraints to include Laravel Zero 13. There are no API changes and no migration work expected. Validate by running the existing test suite and CI matrix against Laravel Zero 13, confirm the resolved dependency graph, and pin versions as usual. Treat this as a compatibility enabler, not a feature release.