Statamic How To Addon Laravel Package

Product Decisions This Supports

• Statamic 4 roadmap planning: v1.5.0 is the first release in the supplied data to claim Statamic 4 support, so it directly affects any upgrade plan where this add-on is a dependency.
• Build vs buy / upgrade vs replace: If the add-on provides commodity CMS functionality, validating the upgrade is likely cheaper than replacing it. If it owns a critical editorial workflow, treat the “untested” compatibility claim as a spike, not production approval.
• Feature and launch decisions: This release adds framework compatibility, not a new product capability. Do not position it externally as a feature launch; position it as a migration enabler pending validation.
• Use cases: Teams running Statamic-based content sites, help centers, or editorial workflows can evaluate v1.5.0 in staging when planning a Statamic 4 move. Avoid making it a launch dependency until compatibility is proven in the actual app.

When to Consider This Package

• Consider it when the application is already on Statamic 4 or planning that upgrade and this add-on is already in the dependency graph.
• Adopt only after running composer update in an isolated branch and smoke-testing admin editing, front-end rendering, permissions, and any custom templates/fields.
• Verify the full compatibility matrix: Statamic 4, Laravel version, PHP version, and any other Statamic add-ons in the stack.
• Look elsewhere—or fork/vendor internally—if the add-on is business-critical and the maintainer’s “untested” note is not followed by tests, CI evidence, or a quick patch cycle.
• Avoid new adoption of v1.5.0 in production without a validation spike; the release notes explicitly state the Statamic 4 support has not been tested.

How to Pitch It (Stakeholders)

• Executives: v1.5.0 is a compatibility release that may remove a Statamic 4 upgrade blocker, but it is not yet a production-ready guarantee. Approve a small validation effort before committing to the platform upgrade.
• Engineering: Treat v1.5.0 as a release candidate. Pin the version in staging, run regression tests around content editing and rendering, and monitor upstream for follow-up fixes.
• Product: Schedule the compatibility spike into the roadmap, but do not promise a Statamic 4 migration date externally until the add-on passes validation in the real application.