From 5e3ea352e7a7c426a125957d83cf7898d7da7175 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Fri, 6 Nov 2026 16:15:09 -0500 Subject: [PATCH] fix: the backup destination migration is 0119, after the existing 0118 Two migrations both claimed revision 0118 on top of 0117, so alembic saw two heads and the upgrade refused to run. Co-Authored-By: Claude Opus 5.5 --- ...up_s3_destination.py => 0119_backup_s3_destination.py} | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) rename alembic/versions/{0118_backup_s3_destination.py => 0119_backup_s3_destination.py} (94%) diff --git a/alembic/versions/0118_backup_s3_destination.py b/alembic/versions/0119_backup_s3_destination.py similarity index 94% rename from alembic/versions/0118_backup_s3_destination.py rename to alembic/versions/0119_backup_s3_destination.py index e2d13a5..2518434 100644 --- a/alembic/versions/0118_backup_s3_destination.py +++ b/alembic/versions/0119_backup_s3_destination.py @@ -4,16 +4,16 @@ Address, bucket, access key and region are plain settings; the secret key is stored sealed with the credential key. All empty means no destination is set up, which is every existing install's state. -Revision ID: 0118 -Revises: 0117 +Revision ID: 0119 +Revises: 0118 Create Date: 2026-11-06 """ import sqlalchemy as sa from alembic import op -revision = "0118" -down_revision = "0117" +revision = "0119" +down_revision = "0118" branch_labels = None depends_on = None