Andras Bacsai 60ef63de54 fix: resolve duplicate migration timestamps and add idempotency guards ...

Two migrations had identical timestamps (2025_10_10_120000), causing non-deterministic execution order and "table already exists" errors during instance startup. Renamed webhook_notification_settings migration to 120002 and added Schema::hasTable() guards to both migrations for idempotency.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-17 14:26:42 +01:00

..

factories

refactor(dashboard): remove deployment loading logic and introduce DeploymentsIndicator component for better UI management

2025-09-30 11:43:30 +02:00

migrations

fix: resolve duplicate migration timestamps and add idempotency guards

2025-11-17 14:26:42 +01:00

seeders

Changes auto-committed by Conductor

2025-10-16 13:45:49 +02:00

.gitignore

init of v4 🌮

2023-03-17 15:33:48 +01:00