Filament Poll Laravel Package

Getting Started

• Confirm your application is already on Filament v5. This release’s only change is Filament v5 compatibility plus the Composer constraint update, so it is an infrastructure upgrade rather than a feature release.
• Upgrade with dependency resolution enabled:

  composer require vendor/package:^2.0 --with-all-dependencies
  

  If Composer reports a conflict, inspect it with:

  composer why-not vendor/package ^2.0
  

• Look first at the package’s composer.json and README for:
  • the exact filament/filament constraint,
  • the plugin/service-provider registration class,
  • any publishable config, assets, or migrations.
• Register the plugin in the relevant Filament panel provider, not globally in AppServiceProvider, so multi-panel applications can opt in per panel:

  public function panel(Panel $panel): Panel
  {
      return $panel
          ->plugin(YourPlugin::make());
  }
  

• First use case: add the upgraded plugin to a non-production panel, clear caches, and smoke-test the panel:

  php artisan optimize:clear
  php artisan filament:upgrade
  

  Then verify login, resource list/create/edit pages, and any widgets or custom pages the plugin provides.

Implementation Patterns

• Upgrade in a branch, not on main. Bump the constraint to ^2.0, run composer update --with-all-dependencies, run your test suite, then manually smoke-test the Filament panel.
• Keep plugin registration panel-specific. In multi-panel apps, register the plugin only on panels that need it. This limits the blast radius of any v5 compatibility issue.
• Publish and own configuration. Publish the package config and keep environment-specific values in .env. Avoid editing vendor files so future patch releases remain safe.
• Treat v2.0.0 as a compatibility major. There are no listed new features or deprecations, so day-to-day usage should be unchanged once you are on Filament v5. If you are still on Filament v4, stay on the previous major and plan the Filament upgrade first.
• Deployment workflow:

  composer install --no-dev --optimize-autoloader
  php artisan migrate --force
  php artisan vendor:publish --tag=package-assets --force
  php artisan optimize
  

  Only republish assets if the package’s assets changed; otherwise keep the deploy minimal.
• Extend through documented hooks. Use the package’s config keys, custom classes, closures, or published views rather than subclassing vendor internals. Filament v5 compatibility may change internal APIs.
• CI coverage. Add or keep a CI job that installs the package against Filament v5 and boots a minimal panel. This catches Composer constraint drift and panel registration failures early.

Gotchas and Tips

• Composer constraint is the main breaking surface. v2.0.0 updates the Filament constraint for v5. If your app is on Filament v4, do not force the upgrade; pin the previous major until your app is ready.
• Check platform requirements. Filament v5 may require newer PHP/Laravel versions. Run composer why-not and review composer.json platform requirements before upgrading.
• Multi-panel apps can behave differently. A plugin registered globally can affect every panel. Register per panel and test each panel’s navigation, resources, and widgets.
• Clear caches after upgrade. Run php artisan optimize:clear and, if applicable, rebuild frontend assets. Stale config or view caches can make the plugin appear broken after a major bump.
• Debugging missing UI: verify the panel provider registration, the plugin’s service provider discovery, and the output of php artisan about / Filament’s panel inspection commands. If the plugin does not appear, check that the correct panel provider is active for the route you are testing.
• Avoid monkey-patching vendor code. Because this release exists specifically to track Filament v5, internal changes may land in patch releases. Prefer config, published views, and documented extension points.
• No feature work expected from this release. If you need new behaviour, check the package’s changelog for later releases rather than assuming v2.0.0 adds functionality.