Upgrade (v4 ↔ v5)
Approval Flows targets Filament v4 and v5 from a single package version (filament/filament: ^4.0 || ^5.0). The same plugin release runs on both, so upgrading Filament rarely touches Approval Flows itself.
Upgrading Filament v4 → v5
-
Follow the official Filament v5 upgrade guide for your app.
-
Bump Approval Flows to the latest release within your license window:
composer update talivio/filament-approval-flows -
Run any new migrations:
php artisan vendor:publish --tag="approval-flows-migrations" --force php artisan migrate--forcere-publishes migration stubs; already-run migrations are skipped by Laravel's migration table. -
Clear caches:
php artisan optimize:clear
Your flows, steps, approvals, and audit history are unaffected — they live in your database, not in Filament.
Staying on Filament v4
You don't have to move to v5. Approval Flows keeps supporting v4 for the life of your update window. Pin Filament in your app's composer.json as usual; the plugin's ^4.0 || ^5.0 constraint won't force an upgrade.
Version compatibility
| Approval Flows | Filament | PHP |
|---|---|---|
| 1.x | v4 & v5 | 8.2+ |
The plugin is tested against both Filament majors on PHP 8.3 and 8.4 in CI.
License & updates
A license includes one year of updates from purchase. After it lapses:
- your installed version keeps working indefinitely,
composer updatestops pulling releases published after your window,- renewing at a discount restores access to newer releases.
Getting help
Hit a snag upgrading? Email support with your Filament and Approval Flows versions and the error, and we'll help you through it.