Product Decisions This Supports
- Laravel 13 upgrade sequencing. This release is a hard dependency gate for any roadmap item that involves moving to Laravel 13. If Laravel 13 is on the platform roadmap, this package must be upgraded first (or in lockstep), and the upgrade should be scheduled as one workstream, not three separate tickets.
- Runtime floor planning. v3.4.0 raises the minimum to PHP 8.3 and Statamic 6.5. That converts "should we move off PHP 8.2?" from an infrastructure nicety into a prerequisite. Budget for the runtime bump and any host/image rebuild as part of the same decision.
- Build vs. buy for form configuration. Form definition/configuration management is commodity capability in a Statamic site. Adopting (or retaining) this package keeps that surface area on the vendor's maintenance cadence rather than your team's — a reasonable trade unless forms become a differentiating product surface.
- Risk reduction on cache behavior. The FormConfig deserialization fix for Laravel 13's hardened cache is the most operationally meaningful line in these notes: without it, form configurations can silently fail to load after a framework upgrade. That is a production-outage class of bug, and having it fixed upstream lowers the cost/risk of the Laravel 13 move.
- Use-case fit. Strong fit for content-managed marketing/brochure sites where editors own form fields. Weak fit for logic-heavy workflows (multi-step branching, payments, complex validation) — those should be treated as application code, not addon configuration.
When to Consider This Package
Adopt (or upgrade to) v3.4.0 when all of the following hold:
- You are on, or actively planning, PHP 8.3+, Statamic 6.5+, and Laravel 12 or 13. The CI matrix (PHP 8.3–8.5, Laravel 12 + 13) is the supported envelope — anything outside it is unsupported.
- Content editors need to define and change forms without engineering involvement.
- You want the serialization allowlist for Statamic's
registerSerializableClasses handled by the package rather than maintained in-house.
Look elsewhere or defer when:
- You are pinned to PHP 8.2 or below, Statamic < 6.5, or Laravel 11 or earlier — 3.4.0 is not installable, and staying on an older line means owning an unsupported branch. Treat this as a fork-or-upgrade decision, not a "wait and see."
- Forms are a core product surface with bespoke logic, integrations, or compliance requirements that the addon's configuration model won't express.
- You need vendor SLAs or guaranteed support windows; this release cadence is tight and version-coupled to Statamic's own majors.
Note for planning: this is a minor version bump with de facto breaking platform requirements. Pin the version explicitly, run the upgrade in a branch, and validate form rendering plus cache warm/read paths — cached FormConfig behavior is exactly what changed.
How to Pitch It (Stakeholders)
To executives: This is a maintenance release that unblocks our Laravel 13 upgrade path and fixes a real configuration-loss risk in the cache layer. It keeps form management with the content team instead of engineering. The cost is a coordinated runtime bump (PHP 8.3+, Statamic 6.5+) that should be folded into the platform upgrade we already need to do — no new initiative required, but it does fix the order of operations.
To engineering: v3.4.0 adds Laravel 13 support and fixes FormConfig deserialization against Laravel 13's hardened cache via Statamic's registerSerializableClasses allowlist. Minimums move to PHP 8.3 and Statamic 6.5. CI now covers PHP 8.3/8.4/8.5 against Laravel 12 and 13. Upgrade order is: PHP runtime → Statamic 6.5+ → this package. Validate cached form config read/write after deploy, since serialization is the changed surface.
Evidence caveat: this assessment is derived from release notes only; no code review, changelog history, or issue-tracker data was available. Confirm the serialization fix under your own cache driver before relying on it.