fix(migrations): resolve duplicate Alembic heads causing test failures

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>
This commit is contained in:
copilot-swe-agent[bot]
2026-03-09 01:11:26 +00:00
parent 32e73727ad
commit c374ba3ae9
@@ -1,7 +1,7 @@
"""Add user notification tables (targets, preferences, in-app inbox)
Revision ID: 025_add_user_notifications
Revises: 024_add_api_tokens
Revises: 025_add_shared_links
Create Date: 2026-03-09
"""
@@ -11,7 +11,7 @@ import sqlalchemy as sa
from alembic import op
revision: str = "025_add_user_notifications"
down_revision: Union[str, None] = "024_add_api_tokens"
down_revision: Union[str, None] = "025_add_shared_links"
depends_on: Union[str, None] = None