Statamic 404 Logger Laravel Package

Product Decisions This Supports

• CMS/Laravel version upgrade planning. v1.1.0 adds Statamic 5 support, which is the gating dependency for teams planning a Statamic 4 → 5 migration. Statamic 5 aligns with modern Laravel (11.x) and PHP 8.2+, so this release directly unblocks the platform-upgrade line item on the roadmap rather than being a nice-to-have.
• Build vs. buy for Statamic-adjacent functionality. A maintained third-party package that tracks the current CMS major version is a credible "buy" against an internal build, because the hidden cost of in-house code is bearing the compatibility burden across every Statamic major. This release is evidence the maintainer is absorbing that cost for you.
• Feature sequencing. If your roadmap includes Statamic 5 features (or depends on Laravel 11), the dependency chain is: upgrade this package → upgrade Statamic → upgrade Laravel. Sequencing that correctly avoids a big-bang migration.
• Vendor/maintenance risk tracking. A minor-version release adding major-CMS compatibility (rather than a paid major or an abandoned repo) is a positive health signal to log in the dependency-risk register.
• Scope caveat for planning: release notes are a single line. Treat this as compatibility evidence, not capability evidence — do not infer new end-user features, performance work, or API changes from v1.1.0 alone. Confirm with the changelog/diff before committing to a delivery date.

When to Consider This Package

Adopt when:

• You are on Statamic and planning or currently executing an upgrade to Statamic 5, and this package sits on that critical path.
• You want Laravel-native integration (service provider, config publishing, Eloquent/Blade conventions) rather than a framework-agnostic library you'd have to wire up yourself.
• You are pre-1.0-shy: the package is past its initial API-churn phase, so the surface is reasonably stable for production use.
• You value a maintainer who ships compatibility releases ahead of or alongside the upstream CMS major, not months after.

Look elsewhere or hold when:

• You are still on Statamic 3 or 4 and not upgrading soon — verify which versions remain supported before adopting, since a minor release adding v5 support can coincide with dropping older majors.
• You are not using Statamic; the package's value proposition is coupled to that platform and the integration surface is dead weight otherwise.
• Your requirements are covered by Statamic core or first-party addons — adding a dependency for parity functionality increases your upgrade matrix for no gain.
• You need guaranteed SLAs or commercial support; validate the maintenance model first.
• The single-line release note is your only evidence. Before adoption, check the README's supported-version matrix, the CI matrix (does it actually test Statamic 5?), and open issues for v5 regressions.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a small, low-risk dependency update with an outsized planning benefit. Version 1.1.0 adds support for Statamic 5, the current major release of our CMS layer. That means the package is not a blocker to our platform upgrade — the upgrade path to a supported, modern Laravel/PHP baseline stays open. It also means we can keep buying this capability instead of building and maintaining it ourselves, which removes a recurring internal maintenance cost across every future CMS upgrade. Recommend: approve the upgrade in the next maintenance window; no new budget required.

For engineering (one paragraph): v1.1.0 is a minor release whose headline change is Statamic 5 compatibility. Treat it as a compatibility bump, not a feature release: confirm the released package's constraints actually permit Statamic 5 (and note any dropped Statamic majors, since minor-version semantics are the maintainer's call, not semver's), run the upgrade on a branch, and verify our usage against the diff. Add a CI job that exercises the Statamic 5 path so we catch the next major early. Risk is low and reversible — pin the previous tag as the rollback.