Laravel Json Ld Laravel Package

Product Decisions This Supports

• Platform-modernization timing (the primary decision). v2.2.0 redraws the support matrix: PHP 8.4/8.5 and Laravel 12/13 are in; PHP 8.1/8.2 and Laravel 9 are out. This is effectively the package's answer to "what runtime floor should our roadmap assume?" Treat it as an input to your upgrade-window decision, not a drop-in routine bump.
• Upgrade sequencing. If any environment (prod, CI, a long-lived client deployment, a legacy queue worker) is still on PHP 8.1/8.2 or Laravel 9, this release is a hard stop for that environment. That converts an invisible dependency update into a visible, plannable migration item — usually the most valuable thing a PM gets from a compat release.
• Build vs. buy / maintenance-cost signal. A package tracking unreleased upstream versions (PHP 8.5 and Laravel 13 are forward-looking targets) is signalling active, forward-leaning maintenance. That lowers the "will this be abandoned on us?" risk and strengthens the buy/keep case versus maintaining an in-house equivalent. Validate the signal against commit cadence and issue-response times before relying on it.
• Semver and version-pinning policy. The release is numbered 2.2.0 — a minor bump — but removes support for two PHP lines and one Laravel major. Under strict semver that is a breaking change that would warrant a 3.0.0. PM decision: mandate exact/compatible version pinning for this dependency and require a read of release notes before any composer update, rather than trusting the caret range.
• Support-matrix as a contract. The package has now effectively committed to a fast-moving trailing edge (drops two PHP minors roughly together). Plan for an annual-or-faster touch on this dependency in your maintenance budget, and note it on the tech-debt register.
• Roadmap dependency check. Confirm no planned feature depends on behaviour only reachable on the now-dropped versions. If a customer-facing commitment was scoped against Laravel 9-era behaviour, that scope is now at risk.

When to Consider This Package

Consider adoption when:

• Your application is on, or committed to, Laravel 12/13 and PHP 8.4+ within a horizon you can actually hit — this release is aimed squarely at you.
• You want a dependency that keeps pace with upstream framework releases rather than lagging a cycle behind; the forward support for PHP 8.5 and Laravel 13 is evidence of that posture.
• You are greenfield or already mid-modernization, so the dropped versions cost you nothing.

Look elsewhere (or stay on the previous release line) when:

• You are pinned to PHP 8.1/8.2 or Laravel 9 with no funded upgrade path. Do not adopt; pin the prior minor and treat the eventual upgrade as a project, not a chore.
• You need a long support tail or an LTS-style guarantee. This package's cadence is aggressive — two PHP lines dropped in a single minor — so it will not shelter you on old runtimes.
• Your release process cannot absorb breaking changes shipped under minor version numbers. That is a process mismatch, and it will bite you again.
• The value you'd get is marginal relative to the upgrade cost; a smaller, slower-moving alternative may be the better trade.

Before committing, verify: the Laravel 13 and PHP 8.5 claims are prospective/experimental rather than fully tested, and that CI actually exercises the versions you run. Forward-declared support is a signal, not a warranty.

How to Pitch It (Stakeholders)

For executives: A dependency we rely on has moved its compatibility floor. It now targets PHP 8.4/8.5 and Laravel 12/13, and has dropped PHP 8.1/8.2 and Laravel 9. The practical consequence is that our upgrade schedule for this component is no longer discretionary — it is now driven by the vendor's cadence, and the work is bounded and well-signposted. No new features are involved; this is a maintenance and risk item, not a capability gain. Recommend we fund a scoped upgrade check this quarter, confirm our runtime versions, and pin the dependency until that check is done.

For engineering: v2.2.0 is a compatibility-only release — no features, no API changes described. It adds PHP 8.4/8.5 and Laravel 12/13 support and removes PHP 8.1/8.2 and Laravel 9. Two cautions: (1) these are breaking removals shipped in a minor version, so pin explicitly and read release notes before updating rather than relying on the caret constraint; (2) PHP 8.5 and Laravel 13 support is likely forward-looking — confirm it is genuinely tested before we plan against it. Action items: audit every environment and CI job for PHP 8.1/8.2 or Laravel 9; pin the current version in the meantime; report the upgrade estimate back so it can be scheduled rather than discovered.