Nova Field Mixins Laravel Package

Product Decisions This Supports

• Framework upgrade / roadmap timing: v3.0.1 confirms Laravel 12 support, so this package is no longer a blocker on a Laravel 12 migration. Teams can sequence the app upgrade without carving out time to fork, patch, or replace the dependency.
• Build vs. buy: a maintained package that tracks current Laravel releases is a "buy" (adopt) signal. The ongoing cost is upgrade lag, not implementation — this release shows the maintainer absorbs that cost for us.
• Dependency risk in the platform budget: a 3.x line receiving same-line patch releases (rather than a major bump to gain Laravel 12) suggests a stable API surface. That lowers the estimate for future upgrade work and reduces the case for internal replacement.
• Release-gating and support policy: gives a concrete justification for a "supported Laravel versions = current + previous" policy in our engineering standards, since the dependency now satisfies it.
• Not implied by this release: no new end-user capability. Do not let this patch release create scope, demo, or launch commitments — it is a compatibility and maintenance signal, not a feature.

When to Consider This Package

Adopt when:

• We are on, or planning, Laravel 12 — this release is the minimum version that makes us current.
• The package's core capability maps to a real roadmap item, and we would otherwise build and own that capability ourselves.
• We want the version-tracking maintenance burden to sit with a third party rather than in our backlog.
• Our dependency review requires declared support for the Laravel version we ship on.

Look elsewhere or defer when:

• Laravel 12 is not on the near-term roadmap — the upgrade alone is not a reason to adopt.
• The package's surface area overlaps with something we already pay for or maintain (duplicate cost, duplicate upgrade cycles).
• The 3.x line has no published deprecation/support policy; "supports Laravel 12 today" says nothing about Laravel 13 timing, which is the risk we actually carry.
• We need guarantees the maintainer cannot give — security response SLAs, LTS commitments, or commercial support.

Before committing, confirm in the changelog/README: minimum PHP version, whether 3.0.x retains the 2.x public API, and the maintainer's stated support window.

How to Pitch It (Stakeholders)

For executives: the package now supports Laravel 12, the current framework release. That means it does not block our platform upgrade, and the maintainer — not our team — is carrying the compatibility work. It is a low-cost adoption with a known, bounded upgrade path; the main risk to track is how quickly future Laravel majors are supported, not this release.

For engineering: v3.0.1 is a patch release adding Laravel 12 support on the 3.x line, so the integration surface is unchanged from v3.0.0 — treat it as a routine dependency bump and pin ^3.0. Validate in staging on Laravel 12 before rollout, and add it to the dependency review checklist so we notice when Laravel 13 support lands. No migration work is expected; flag any deprecation notices surfaced by our own test suite.