c374ba3ae9
Two migration files (025_add_shared_links and 025_add_user_notifications) both had down_revision pointing to 024_add_api_tokens, creating multiple migration heads. This caused alembic stamp/upgrade head to fail with 'Multiple heads are present; please specify a single target revision' whenever init_db() ran (e.g. in TestClient fixtures). Fix: chain 025_add_user_notifications from 025_add_shared_links so the migration history is linear: 024_add_api_tokens → 025_add_shared_links → 025_add_user_notifications Co-authored-by: christianlouis <361235+christianlouis@users.noreply.github.com>
Generic single-database configuration.