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 <noreply@anthropic.com>
2026-11-06 16:15:09 -05:00
parent 4477d7d14f
commit 5e3ea352e7
1 changed files with 4 additions and 4 deletions
@@ -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