Statamic Clear Assets Laravel Package

Product Decisions This Supports

• Upgrade gating for the platform roadmap. v3.4.0 is a compatibility-only release that adds Laravel 13.x support. This is the unblocker that lets you schedule a Laravel 13 upgrade without dropping asset-cache clearing from your editorial workflow.
• Build vs. buy for cache invalidation. The package solves a narrow, well-defined problem: clearing Statamic's asset/Glide caches so editors don't see stale images after replacing a file. This release does not change the build-vs-buy calculus — it remains a small, single-purpose addon you would not build in-house.
• Dependency risk tracking. The change came from an external contributor (@laravel-shift, the Laravel automated-upgrade tooling account) rather than the maintainer. Treat this as a signal that the package's continued viability depends on automated upstream compatibility work, not active feature development.
• Not a feature release. There are no new capabilities, configuration options, or behaviour changes here, so it should not drive any product-facing roadmap item, demo, or documentation update.

When to Consider This Package

Adopt when all of the following hold:

• You run Statamic (this is a Statamic addon, not a generic Laravel package) and editors regularly replace assets where the old Glide-derived image variants linger in cache.
• You are on, or planning to move to, Laravel 13.x — that is the only thing this release changes.
• You want invalidation wired into the control panel or a simple command rather than hand-clearing cache directories.

Look elsewhere or hold when:

• Statamic version compatibility is unstated. The release notes confirm Laravel 13 but say nothing about which Statamic major is supported. Verify the composer.json constraints before committing — a Laravel-only bump can still break against a new Statamic release.
• You need active maintenance. One compatibility PR per cycle with no other activity is a low-velocity project. If asset cache staleness is business-critical (e.g. commerce, regulated content), consider a thin in-house command as a hedge.
• Your caching is already solved by deploy-time cache clearing or a CDN purge step; the addon would be redundant.
• You are not on Laravel 13. If you are on 11.x or 12.x, there is no functional reason to take this release; stay pinned and upgrade in step with your framework.

How to Pitch It (Stakeholders)

For executives: A small, low-cost addon we rely on for a specific editorial annoyance — stale images after asset replacement — has been updated to work with the newest Laravel version. This removes a blocker from our framework upgrade path. No new spend, no new features, no user-facing change.

For engineering: v3.4.0 adds Laravel 13.x compatibility only, contributed via an automated upgrade PR. There are no breaking changes, no new APIs, and no deprecations. Action: confirm the addon's Statamic constraint matches our target Statamic version, then bump the pin as part of the Laravel 13 upgrade ticket. Because the project shows minimal maintainer activity, keep the upgrade scoped and be prepared to vendor or replace the cache-clearing logic if it lags a future Laravel or Statamic major.