Product Decisions This Supports

CMS/platform upgrade planning: v1.0.1 adds Statamic 4 support, which unblocks teams planning a Statamic 3 → 4 (and corresponding Laravel 9/10) upgrade without dropping this package from the stack. A PM can treat this as a green light for the addon to stay in the migration scope rather than be replaced.
Build vs. buy: A compatibility release signals active maintenance. If the capability this package provides is on your roadmap, buying/adopting is now lower risk than building an in-house equivalent that you would also have to keep compatible with Statamic 4.
Vendor and dependency risk: The package is at 1.0.x, meaning the API is stabilizing but not yet mature. This release is a maintenance/compatibility patch rather than a feature drop, so it reduces "abandoned dependency" risk but does not resolve "young dependency" risk.
Support-window compliance: Staying on Statamic 4 keeps the product on a supported CMS line; this release lets you make that decision without carrying an unsupported addon forward.
Release scoping: Because v1.0.1 is a narrow compatibility change, it can be bundled into a routine maintenance sprint rather than requiring its own roadmap slot.

When to Consider This Package

Adopt when: you are on (or migrating to) Statamic 4 and this package covers a capability you need; you want an addon that has demonstrated it tracks upstream Statamic releases; and you can tolerate a 1.x API.
Adopt with caution when: you are still on Statamic 3 — confirm the new release retains backward compatibility rather than replacing Statamic 3 support, and check the package's version constraints. Also confirm the Laravel/PHP versions it supports match your runtime.
Look elsewhere when: you are not on Statamic; you need a mature, long-supported dependency with a stable public API and a proven upgrade history; you require enterprise support/SLAs; or a single-maintainer 1.0.x addon is unacceptable for a business-critical path.
Before committing: validate the actual release contents (composer constraints, CI matrix, changelog, open issues) — the release note alone is thin evidence of quality.

Executives: "This is a small maintenance release that adds compatibility with the current version of our CMS platform. It keeps our stack on a supported version at effectively no cost and removes a blocker from our upgrade plan."
Engineering: "v1.0.1 is a compatibility patch adding Statamic 4 support. Verify the composer constraints and CI matrix, confirm Statamic 3 support is retained if we still need it, run it through our upgrade branch, and pin the version. It's a 1.0.x package, so treat the API as stabilizing and watch the changelog."
One-line summary: Low-risk compatibility update that keeps a young but actively maintained Laravel/Statamic addon viable through a platform upgrade — adopt if the capability fits, but validate scope and support matrix before relying on it in a critical path.