Statamic Peak Browser Appearance Laravel Package

Product Decisions This Supports

• Platform upgrade sequencing (Statamic v6). v4.0.0 adds Statamic v6 support, which makes this package a viable dependency in a Statamic 6 migration. This is the primary product decision it unblocks: whether the v6 upgrade path is clear or blocked by addon lag.
• Build vs. buy for global-variable tooling. The package's value is in extending Statamic's global variables/global sets with lifecycle awareness (now via the GlobalVariablesSaved event). If your roadmap includes editorial-managed global content that needs to trigger side effects (cache busting, search indexing, CDN purges, downstream syncs), adopting this is cheaper than building event plumbing yourself — provided the package's scope matches that need.
• Integration surface for downstream features. Event-driven hooks on global variable saves mean features like "content changes invalidate X" can be scoped as configuration rather than custom code. That changes effort estimates for personalization, syndication, or cached-fragment work.
• Dependency risk review. A v4.0.0 major bump within days/weeks of an upstream major is a positive maintenance signal, but it also means a version-pinning decision lands on the roadmap: v3.x for Statamic 5 projects, v4.x for Statamic 6.

Caveat for planning: this release note is two commits by a single maintainer. Treat the upgrade as "likely fine, verify in a branch" rather than "certified for production" — there is no stated test-matrix evidence, no changelog history, and no deprecation notice.

When to Consider This Package

Adopt when:

• You are on Statamic 6 (or actively migrating) and need global variables/global sets to participate in application lifecycle events.
• You want save-time hooks on global content without writing and maintaining your own Statamic event listeners.
• You value an addon that tracks upstream majors promptly — a same-cycle v6 release is a reasonable proxy for maintenance health.

Look elsewhere / defer when:

• You are still on Statamic 5. v4.0.0 is a major version; assume it does not support v5 and pin v3.x. Confirm the compatibility matrix before assuming either direction.
• You only need core Statamic global sets. This package is an extension, not a replacement — if you have no event-driven requirement, you are buying maintenance overhead for nothing.
• You rely on your own listeners around global variable saves. The move to GlobalVariablesSaved can change event timing, payload, or class name; existing listeners need an audit.
• You require vendor-grade guarantees: single-maintainer, small-commit-count releases with no published test coverage or security policy are a procurement risk for regulated or high-traffic surfaces.

Required verification before commitment: confirm which Statamic versions v4.x actually supports, whether GlobalVariablesSaved is additive or a rename (renames break listeners silently), and whether the change affects save-time ordering relative to core Statamic events.

How to Pitch It (Stakeholders)

To executives: This is a small Statamic addon that handles global content variables and has just shipped support for Statamic 6 — the current major version of our CMS. That matters because our CMS upgrade is only as fast as our slowest addon; a maintainer shipping on the v6 cycle removes a blocker and reduces the chance we get stranded on an unsupported version. It is a low-cost, low-blast-radius dependency, but it is maintained by one person, so we should treat it as a tracked dependency rather than a load-bearing one.

To engineering: v4.0.0 is a major version gated on Statamic 6 support, plus a migration to the GlobalVariablesSaved event. Two action items: (1) pin v3.x on Statamic 5 and v4.x on Statamic 6 — do not assume cross-compatibility; (2) audit any existing listeners around global variable saves, as the event change may rename or reorder them. Scope is roughly a half-day: branch upgrade, smoke-test global variable saves and their downstream side effects (cache, search, CDN), then promote. No deprecations or security items flagged in this release.

Recommendation: Adopt on Statamic 6 projects where global-variable lifecycle hooks are already required; otherwise hold and re-evaluate at the next release, when there is more evidence of v6 stability.