Zmkr Cloudflare Turnstile Bundle Laravel Package

Product Decisions This Supports

• Platform upgrade planning: v2.0 sets a PHP 8.2 minimum and Symfony 5.4 minimum. This aligns with Laravel 11/12 requirements and gives a clear trigger to retire PHP 8.0/8.1 from our support matrix.
• Build vs. buy: The release shows active maintenance — Symfony 8 readiness, contribution guidelines, PHP CS Fixer, PHPStan fixes, Composer test helpers. That reduces the case for forking or building an in-house replacement.
• Roadmap input: Symfony 8 support is forward-looking. It lets us test against the next major Symfony line that future Laravel releases will inherit, informing when we schedule framework upgrades rather than reacting to them.
• Feature and use-case fit: Relevant to Laravel applications that depend on Symfony components (HTTP foundation, console, process, etc.), and to shared PHP services where Laravel and standalone Symfony code coexist.
• Tooling standardization: The added formatting and static-analysis support is a signal we can standardize CI (PHP CS Fixer + PHPStan) across repos that consume this package.

When to Consider This Package

• Adopt v2.0 if: the application is on PHP 8.2+ and Laravel 10+ (Symfony 6.x components or later), and the team wants a maintained dependency with Symfony 8 readiness.
• Adopt if: you need dual compatibility across Laravel and standalone Symfony services, or you want upstream contribution and static-analysis hygiene as a risk-reduction signal.
• Stay on v1.x if: any service still runs PHP 8.0/8.1 or Symfony < 5.4. v2.0 is a hard breaking change for those environments and requires a coordinated platform bump first.
• Look elsewhere if: the package does not document Laravel integration (service provider, config publishing) for your version, or if your platform cannot move to PHP 8.2 within the current support window.
• Treat as a scheduled upgrade, not an emergency: the breaking changes are runtime floors, not API rewrites — but they still require an inventory of affected services before adoption.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, low-risk dependency upgrade that keeps us on supported PHP versions and avoids an emergency migration later. The maintainers are active — new Symfony support, contribution guidelines, and automated quality tooling — which lowers long-term maintenance risk and bus factor.

For engineering: v2.0 is a breaking release, but the break is scoped to minimum runtime versions: PHP 8.2+ and Symfony 5.4+. Plan it alongside the PHP 8.2 rollout, add a CI matrix covering PHP 8.2/8.3/8.4 and Symfony 5.4/6/7/8, and adopt the provided CS Fixer and PHPStan configuration. Confirm no production service remains below the new floors before merging.

Ask: Approve an upgrade ticket for the next sprint, gated on a PHP-version inventory and a green CI matrix.