Brandgeo Laravel Nova Laravel Package

Product Decisions This Supports

• Upgrade/adoption decision: v1.1.0 is a low-risk minor release that broadens compatibility to a2zwebltd/brandgeo-laravel-client ^1.0|^2.0, reducing friction for teams planning a client upgrade or already on v2.
• Customer-facing reliability: Unknown subscription statuses now render a neutral grey plan badge instead of throwing UnhandledMatchError, which supports shipping subscription UI with fewer edge-case crashes.
• Build vs. buy: If you need a lightweight Laravel plan badge backed by BrandGeo subscription data, this package can replace a small custom Blade component and some defensive rendering code.
• Roadmap signal: The release shows maintainer focus on forward compatibility and graceful degradation, both positive indicators for teams standardizing on the BrandGeo client.

When to Consider This Package

• You use Laravel and already depend on, or plan to adopt, a2zwebltd/brandgeo-laravel-client.
• You need a simple UI badge for subscription plan status and want sensible fallback behavior for unknown statuses.
• You want compatibility across BrandGeo client v1 and v2 without maintaining a fork.
• Look elsewhere if you need full billing/entitlement UI, multi-provider subscription support, strict alerting on unexpected statuses, or a broader subscription management feature set beyond badge rendering.

How to Pitch It (Stakeholders)

For executives: This is a small maintenance release that lowers risk in customer-facing subscription UI: unknown statuses degrade to a neutral badge instead of breaking the page, and the package supports both current and next BrandGeo client versions. No new infrastructure or operational burden.

For engineering: Upgrade is likely safe. v1.1.0 widens the client constraint and replaces an UnhandledMatchError with a grey fallback badge for unknown statuses. Validate badge rendering against your installed client version, and confirm whether you want silent fallback vs. monitoring for unexpected statuses.