Statamic Boost Laravel Package

Product Decisions This Supports

• Upgrade timing and platform roadmap: v1.3.0 adds fresh-install CI coverage for PHP 8.5, Laravel 13, Statamic 6, and Laravel Boost 2. This is evidence that the package is actively tracking the next major platform combinations, reducing uncertainty when planning Laravel/Statamic upgrades.
• Build vs. buy / adopt vs. maintain in-house: The release improves the package’s operational maturity — installer failure handling, Statamic environment preservation during Boost configuration rebuilds, and fieldtype discovery/Antlers guideline fixes. That strengthens the case for adopting the package rather than maintaining custom Boost/Statamic integration glue.
• AI-assisted development readiness: Fixes to generated AI guidelines, fieldtype discovery, and Antlers examples directly affect the quality of AI-generated code and documentation for Statamic projects. This supports decisions to standardize AI guidance across teams using Laravel Boost and Statamic.
• Documentation and support operations: The new weekly documentation update process, read-only documentation dry runs on pull requests, and tracking issues for newly detected majors establish a repeatable documentation release baseline. PMs can treat documentation freshness as an ongoing product capability rather than ad hoc maintenance.
• Release cadence planning: Because documentation changes can now publish minor releases weekly, teams should expect more frequent minor versions. This supports decisions around version pinning, upgrade cadence, and dependency review policies.

When to Consider This Package

• Consider it when the product uses Statamic with Laravel Boost / Laravel MCP, especially if teams rely on generated AI guidelines, fieldtype discovery, or Antlers examples.
• Consider it when planning or validating upgrades across Laravel 13, PHP 8.5, Statamic 6, and Boost 2, since this release explicitly adds fresh-install CI coverage for that matrix.
• Consider it when installer reliability and configuration stability matter — particularly preserving the selected Statamic environment when Boost rebuilds configuration.
• Consider it when documentation freshness is important and the team can accommodate weekly minor documentation releases through normal dependency review and pinning practices.
• Look elsewhere when the product is not using Statamic, Laravel Boost, or MCP-based tooling; when the team requires a slow, infrequent release cadence; or when adopting a small integration package would add more dependency-management overhead than the workflow value it provides.

How to Pitch It (Stakeholders)

For executives: This release strengthens confidence in the Statamic/Laravel Boost integration by adding CI coverage for upcoming platform versions and improving installer/config reliability. It also establishes an automated documentation release process, which reduces documentation drift and support risk. The main trade-off is a faster minor-release cadence for documentation changes, which should be managed with standard version pinning and dependency review.

For engineering: v1.3.0 is a maintenance and readiness release, not a breaking-change release. It fixes Boost 2/Laravel MCP compatibility, preserves Statamic environment selection during configuration rebuilds, improves installer failure reporting, and fixes generated AI guideline issues. The new CI matrix and documentation automation give us better signals for Laravel 13, PHP 8.5, Statamic 6, and Boost 2 compatibility. Recommend adopting or upgrading with normal review, pinning versions where needed, and watching the weekly documentation minor releases.