Filament Swiper Laravel Package

Product Decisions This Supports

• Laravel 12 upgrade planning: This release is a compatibility patch — filament-swiper (a Filament plugin wrapping Swiper.js) now declares support for Laravel 12. If a Laravel 12 / Filament upgrade is on the roadmap, this package no longer blocks it, and conversely, if we pin to Laravel 11 we are not yet forced to adopt anything.
• Build vs. buy for carousel/slider UI: Any feature that needs a swipeable gallery, hero carousel, testimonial rotator, or product image slider inside a Filament admin panel is a candidate for this package instead of a hand-rolled Alpine/JS component. This release doesn't change that calculus, but it keeps the "buy" option viable for the next upgrade cycle.
• Dependency risk register: The release is a single PR from a first-time contributor with a beta version tag — a signal to log the package as low-bus-factor, beta-channel in our dependency inventory, and to decide deliberately whether the admin UI surface it touches is "nice to have" or "revenue-critical."
• Release/versioning policy enforcement: It's still 3.0.x-beta. That constrains how we consume it (see below) and is a decision point on whether beta-tagged packages are allowed in production panels at all.

When to Consider This Package

Consider it when:

• You are on (or moving to) Laravel 12 with a Filament v3 admin panel and need a slider/carousel without writing and maintaining the JS glue yourself.
• The slider is confined to the admin/back-office surface, where a visual regression is recoverable and not customer-facing.
• You want Swiper.js specifically (touch gestures, loop, autoplay, responsive breakpoints) rather than a bespoke component.
• You can pin the exact version and tolerate a thin maintainer footprint — the upstream project is small, and this release is a first-time-contributor PR.

Look elsewhere when:

• The slider is on a customer-facing storefront or a conversion-critical page — a beta-tagged, single-maintainer Filament plugin is the wrong risk profile there.
• You need guaranteed long-term support, security response SLAs, or a vendor to escalate to. There is no commercial backing here.
• Your stack is not Laravel 11/12 + Filament v3, or you're on an older Filament major — compatibility is version-narrow and this patch only widens the Laravel ceiling, not the Filament floor.
• A trivial static gallery would do: adding a JS dependency, a plugin, and an upgrade surface for four images is not a good trade.

Practical adoption stance: pin exactly (3.0.5-beta), keep it behind an admin-only boundary, and treat each beta bump as a reviewable event rather than an auto-merge — the version tag alone means the maintainer reserves the right to break things between minors.

How to Pitch It (Stakeholders)

To executives: This is a small housekeeping release, not a feature. The one substantive change is that a third-party slider plugin used in our admin interface now officially supports Laravel 12, which removes a blocker from our framework upgrade path. It costs us nothing to take and nothing to skip. The real message is a risk one: this dependency is maintained by a very small team, ships only beta versions, and this release came from a first-time contributor — so we should keep it confined to internal admin screens and out of anything customer-facing until it has a stable release and a longer track record.

To engineering: filament-swiper 3.0.5-beta adds Laravel 12 support (PR #15, new contributor @itaginsexordium) on top of 3.0.4-beta — no API, config, or asset changes, no deprecations, and no migration work. Treat it as a compatibility confirmation, not an upgrade. Pin the exact version, keep the panel usage admin-only, and note that the -beta suffix on the whole 3.x line means we should review changelogs on every bump rather than floating the constraint. If the Laravel 12 upgrade is scheduled, this package is now clear; if it isn't, there is no urgency to move.