From af52fe0cade465bb248684a1c0f8e95e86a921cf Mon Sep 17 00:00:00 2001 From: bboysoul Date: Sun, 20 Sep 2026 14:11:06 +0800 Subject: [PATCH] fix: add tombstone migration for reverted calendar subscriptions --- .../versions/0020_calendar_subscriptions.py | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 migrations/versions/0020_calendar_subscriptions.py diff --git a/migrations/versions/0020_calendar_subscriptions.py b/migrations/versions/0020_calendar_subscriptions.py new file mode 100644 index 0000000..93e5f96 --- /dev/null +++ b/migrations/versions/0020_calendar_subscriptions.py @@ -0,0 +1,28 @@ +"""tombstone for reverted calendar subscriptions + +Revision ID: 0020_calendar_subscriptions +Revises: 0019_backup_imports + +The calendar subscription feature (backend/calendar.py, backend/calendar_router.py) +was reverted from main, but this revision id was already applied to the production +database. Keeping an empty migration under the same revision id lets +`alembic upgrade head` succeed on databases stamped at this revision. +""" + +from alembic import op # noqa: F401 + +revision = "0020_calendar_subscriptions" +down_revision = "0019_backup_imports" +branch_labels = None +depends_on = None + + +def upgrade() -> None: + # Intentionally empty: the feature was reverted. The leftover + # calendar_subscriptions table on already-migrated databases is harmless + # and intentionally left in place. + pass + + +def downgrade() -> None: + pass