jeffersongoncalves/filament-kanban
A Filament plugin that adds interactive KanBan boards to your Laravel admin panel, letting you organize records into draggable columns, reorder cards, and manage status workflows with configurable board and card views for flexible project and task management.
This is a patch release (2.0.1) for a Laravel/Filament package — jeffersongoncalves/filament-help-desk — that fixes a production-only rendering failure. The architectural signal matters more than the patch size: the package had been shipping board layout as raw Tailwind utility classes inside vendor views. Because host Laravel apps do not scan vendor/ paths in their Tailwind content configuration, production builds purged those classes and the board collapsed to an unstyled flat list. The fix registers the layout as a stylesheet through Filament’s FilamentAsset mechanism instead of relying on the host app’s Tailwind pipeline.
Architecture fit. This is correct for the Filament ecosystem. Filament plugins should ship their own compiled/registered assets rather than assume host Tailwind content scanning. The change aligns the package with Filament’s asset registration model and reduces coupling to the host app’s frontend build. For a TPM, this is a positive architectural correction: it moves the package from “works only if the host configures Tailwind to scan vendor files” to “self-contained asset registration.”
Integration feasibility. High for existing Filament v3/v4-style stacks, assuming the package already declares compatible Filament and Laravel constraints. The fix is a patch-level change and should not require application code changes. The main integration checks are: Filament asset registration works in the host panel provider, asset publishing/caching behaves correctly, and production builds no longer depend on vendor view scanning.
Technical risk. The immediate regression risk is low, but the release exposes a previous latent production-only failure mode. Any host app that had worked around the old behavior — for example by adding vendor paths to Tailwind content, manually publishing views, or overriding board styles — should verify it does not double-apply or conflict with the new registered stylesheet. The bigger risk is process: this bug only appeared in production builds, so the package’s release validation likely lacked a production asset build test. A TPM should treat that as a quality-gate concern, not just a one-off bug.
Key questions.
php artisan filament:assets or vendor:publish in host apps, or is registration automatic?vendor/jeffersongoncalves/filament-help-desk to Tailwind content as a workaround, and will those now conflict?Stack fit. Suitable for Laravel applications using Filament panels. The package belongs in the “Filament plugin” layer: installed via Composer, registered in a panel provider, and now self-registering its board stylesheet via FilamentAsset. Host apps should not need to modify Tailwind configuration for this package after 2.0.1.
Migration path. Treat this as a low-risk patch upgrade from 2.0.0. Recommended path: update Composer constraint to 2.0.1, run composer update jeffersongoncalves/filament-help-desk, clear cached Filament assets and application caches, rebuild frontend assets in production mode, and verify the board page in a production-like environment. If the host app previously added vendor paths to Tailwind content specifically for this package, remove that workaround after confirming the board renders correctly.
Compatibility. Because the fix uses FilamentAsset, compatibility depends on the Filament version the package targets. Confirm the package’s Composer constraints before upgrading. If the host app is on an older Filament version that does not expose the same asset registration API, this patch may not be installable or may behave differently. There should be no database migration or API compatibility concern based on the release note, but that should be confirmed against the package changelog.
Sequencing. Upgrade in a branch or staging environment first. Validate the board in both npm run dev and npm run build modes, because the original defect only manifested after Tailwind purging. Then verify Filament’s asset publishing/caching commands in the deployment pipeline. Only after that should production be updated. If the host app has custom board styling overrides, test those explicitly before and after the upgrade.
Maintenance. The fix reduces long-term maintenance burden by removing an implicit dependency on host Tailwind configuration. However, it also means the package now owns its stylesheet registration, so future style changes must go through Filament’s asset pipeline. Maintenance teams should know that this package is not intended to be styled via host Tailwind scanning.
Support. Expect fewer “board is unstyled in production” reports after 2.0.1, but support may see cases where host apps had workarounds in place. Support documentation should call out: clear Filament assets after upgrade, rebuild production assets, and remove vendor Tailwind scanning workarounds if present.
Scaling. No meaningful scaling concern from this patch. Asset registration is a build/deploy concern, not a runtime scaling concern. The more relevant scaling issue is release quality: if the package previously shipped a production-only rendering bug, maintainers should add a production asset build check to prevent similar issues as usage grows.
Failure modes. The main failure mode is host apps not republishing or recaching Filament assets after upgrade, leaving stale asset references. A secondary failure mode is conflict with existing host workarounds that manually scanned vendor views or overrode board styles. There is also a deployment-order risk: if frontend assets are rebuilt before the package update is deployed, or vice versa, the board may render incorrectly until caches are cleared.
Ramp-up. Low for teams already using Filament. The key ramp-up item is understanding Filament’s asset registration and publishing lifecycle. Teams new to Filament should be shown the panel provider registration, filament:assets command, and the difference between package-provided assets and host-compiled Tailwind assets. For a TPM, the main takeaway is that 2.0.1 is a necessary production correctness fix, not a feature release, and the upgrade should be scheduled with a production-mode rendering check.
How can I help you explore Laravel packages today?