fix: the backup destination migration is 0119, after the existing 0118
CI and images / lint (push) Successful in 1s
CI and images / extension-version (push) Successful in 2s
CI and images / frontend-build (push) Successful in 21s
CI and images / extension-test (push) Successful in 23s
CI and images / backend-lint-and-test (push) Successful in 44s
CI and images / integration (push) Successful in 2m21s
CI and images / sign-extension (push) Successful in 2s
CI and images / build-agent (push) Successful in 4s
CI and images / build-web (push) Successful in 2m8s
CI and images / smoke-web (push) Successful in 48s
CI and images / promote (push) Successful in 2s
CI and images / refresh-dev (push) Skipped
CI and images / unattended-failure (push) Skipped

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>
This commit is contained in:
2026-11-06 16:15:09 -05:00
co-authored by Claude Opus 5.5
parent 4477d7d14f
commit 5e3ea352e7
@@ -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 stored sealed with the credential key. All empty means no destination is set
up, which is every existing install's state. up, which is every existing install's state.
Revision ID: 0118 Revision ID: 0119
Revises: 0117 Revises: 0118
Create Date: 2026-11-06 Create Date: 2026-11-06
""" """
import sqlalchemy as sa import sqlalchemy as sa
from alembic import op from alembic import op
revision = "0118" revision = "0119"
down_revision = "0117" down_revision = "0118"
branch_labels = None branch_labels = None
depends_on = None depends_on = None