TenantAtlas/specs/102-filament-5-2-1-upgrade/quickstart.md
ahmido 8f8bc24d1d feat: upgrade Filament to v5.2.1 (#124)
What: Upgrade Filament auf v5.2.1 (inkl. composer.lock + veröffentlichte Filament assets unter public), SpecKit-Doku unter specs/102-..., plus kleine Anpassungen in Tests + Tenant-Scoping in BackupSetResource.
Verification: vendor/bin/sail bin pint --dirty --format agent (pass) + vendor/bin/sail artisan test --compact [AlertDeliveryViewerTest.php](http://_vscodecontentref_/6) tests/Feature/Filament/BackupSetGraphSafetyTest.php (pass)
Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #124
2026-02-20 12:20:42 +00:00

42 lines
1.3 KiB
Markdown

# Quickstart: Filament v5.2.1 Upgrade Verification
## Preconditions
- Baseline on `dev` is green (tests passing) before applying the upgrade.
- Local environment uses Sail.
## Local verification (early signal)
1. Bring up services: `vendor/bin/sail up -d`
2. Install dependencies from lock: `vendor/bin/sail composer install`
3. Run automated gate:
- Full suite: `vendor/bin/sail artisan test --compact`
- Frontend build: `vendor/bin/sail npm run build`
## Staging verification (required gate)
Run the UI smoke on staging after deploying the upgrade artifact.
Must-pass smoke (time-box ≤ 10 minutes):
- Auth: login/logout for Admin panel; verify System panel access if present
- Navigation: load key sections in `/admin` and `/system` without errors
- Tenancy behavior: verify no unexpected tenant scoping/registration in `/system`; verify tenant context works as expected in `/admin`
- Tables:
- search + filters
- bulk actions
- “Select all” (including correctness with any non-selectable rows)
- Modals: create/edit, confirmation dialogs
## Rollback
Primary rollback mechanism:
- Revert `composer.lock` (and any Filament constraint change in `composer.json`) to the last known-good state.
- Redeploy the prior known-good artifact.
Success criteria:
- Tests + build return to green
- Staging UI smoke passes again