Filament Bandel Laravel Package

Product Decisions This Supports

• Filament upgrade sequencing. v3.0.0 supports Filament 3, 4 and 5 from a single branch via runtime version detection. This removes the admin-panel moderation UI as a blocker in a Filament 4/5 migration plan — one dependency line covers all three majors, so the roadmap can schedule the Filament bump without waiting on a separate package release.
• Build vs. buy for moderation tooling. The scope is deliberately narrow (four table actions plus a shared ban form schema). Buying is justified only because of the cross-version maintenance burden; hand-rolling the same actions is a day of work but becomes a recurring tax on every Filament major. Treat this as a cheap hedge, not a platform decision.
• Scope boundary for trust & safety features. The package covers issuing bans (single and bulk) and unban, with expired_at validation preventing accidental permanent/backdated bans. It does not cover appeals, audit history, notifications, or IP/device bans. Use it as the admin control surface on top of an existing ban model, and budget separately for any moderation workflow beyond that.
• Data-integrity posture for bulk admin actions. The bulk operations now re-read record state from the database before filtering, run inside a transaction, and validate form input. This makes bulk ban/unban safe to expose to support staff rather than restricting it to engineers — a support-ops decision, not just a bug fix.
• Dependency floor as a portfolio constraint. Requiring PHP 8.2+ and Laravel 11.8+/12/13 (Laravel 10 dropped) is the deciding input for whether this release lands now or waits for the platform upgrade. Check this against every app that shares the admin panel before adopting.

When to Consider This Package

Adopt when all of the following hold:

• You run a Filament 3, 4 or 5 admin panel and expect to move across those majors within the next year or two.
• Your user model already uses a laravel-ban-style trait with a banned_at column and observers — the package's semantics (and its bulk-freshness fix) assume that model.
• You need only the standard moderation verbs: ban, unban, bulk ban, bulk unban, with an optional expiry.
• Your platform is on PHP 8.2+ and Laravel 11.8+.

Look elsewhere or stay put when:

• You're on Laravel 10 or PHP 8.1. v3 is a hard break with no compatibility shim; pin to v2.x until the platform moves, and note that v2.x will not track Filament 5.
• You need to subclass the actions. Action classes are now final and make() no longer accepts a custom name — custom naming or behaviour must be expressed by chaining after make(). Any existing fork or subclass is now a migration item, not a drop-in.
• You need moderation features beyond the verbs above — appeals, ban reasons history, moderator attribution, IP bans, notification hooks. That's a different product; don't stretch this one.
• Your ban logic is bespoke (custom trait, soft-delete-based, external auth provider). The observer-driven banned_at assumption is load-bearing here.
• You need vendor assurance. This is a single-maintainer package with a small surface area. That's acceptable for a thin admin UI; it is not acceptable if moderation is a regulated or revenue-critical control.

Adoption guidance: pin the version, run the upgrade on a branch, and exercise bulk ban/unban against real data — the freshness and transaction changes are the behaviours most worth confirming in staging.

How to Pitch It (Stakeholders)

To executives: This is a small, low-cost dependency that adds ban/unban controls to our admin panel and, more importantly, keeps working across the next two Filament versions without us maintaining it ourselves. The v3 release also fixes a correctness bug where bulk bans could skip or double-apply. Cost is one dependency; the benefit is removing a known blocker from our admin-panel upgrade path.

To engineering: v3.0.0 is a maintenance and correctness release with breaking changes. It targets Filament 3/4/5 from one branch by resolving action namespaces at runtime, so we stop carrying per-major forks. It requires PHP 8.2+ and Laravel 11.8+, and drops Laravel 10 — confirm our floor before bumping. Action classes are final and make() no longer takes a name, so any subclassing or custom naming becomes chaining after make(). Bulk operations now re-read records from the database and run in a transaction, which addresses the stale-model bug caused by ban observers writing banned_at to separate instances. Test coverage was rebuilt on Pest with testbench and a CI matrix across Filament 3/4/5 × Laravel 11/12/13, which materially raises confidence versus v2.