mirror of
https://github.com/langgenius/dify.git
synced 2026-09-05 08:48:10 +08:00
fix(api): restore deploy/dev alembic revision c8e7f6a5b4d3
The deploy/dev database is stamped at empty merge revision c8e7f6a5b4d3, which disappeared after deploy/dev was rewritten. Reintroduce that revision on top of remove_agent_drive and merge it with the current head so flask db upgrade can locate the DB and apply the migrations that landed after 20 Aug.
This commit is contained in:
parent
ff260f9be3
commit
ae77dd29da
@ -0,0 +1,26 @@
|
||||
"""restore deploy/dev alembic revision c8e7f6a5b4d3
|
||||
|
||||
Revision ID: c8e7f6a5b4d3
|
||||
Revises: 89919253ca7a
|
||||
Create Date: 2026-08-20 15:45:00.000000
|
||||
|
||||
The deploy/dev database is stamped at this revision. The original file
|
||||
was an empty merge of skill/debug heads and later disappeared when
|
||||
deploy/dev was rewritten. Keep the revision id so flask db upgrade can
|
||||
locate the database, and parent it at remove_agent_drive — the last
|
||||
shared revision that was actually applied — so later migrations still run.
|
||||
"""
|
||||
|
||||
# revision identifiers, used by Alembic.
|
||||
revision: str = "c8e7f6a5b4d3"
|
||||
down_revision = "89919253ca7a"
|
||||
branch_labels = None
|
||||
depends_on = None
|
||||
|
||||
|
||||
def upgrade() -> None:
|
||||
pass
|
||||
|
||||
|
||||
def downgrade() -> None:
|
||||
pass
|
||||
@ -0,0 +1,21 @@
|
||||
"""merge c8e7f6a5b4d3 onto current deploy/dev head
|
||||
|
||||
Revision ID: ae0c8e7b4d31
|
||||
Revises: c8e7f6a5b4d3, 5578e028b2f2
|
||||
Create Date: 2026-09-01 17:48:00.000000
|
||||
|
||||
"""
|
||||
|
||||
# revision identifiers, used by Alembic.
|
||||
revision: str = "ae0c8e7b4d31"
|
||||
down_revision = ("c8e7f6a5b4d3", "5578e028b2f2")
|
||||
branch_labels = None
|
||||
depends_on = None
|
||||
|
||||
|
||||
def upgrade() -> None:
|
||||
pass
|
||||
|
||||
|
||||
def downgrade() -> None:
|
||||
pass
|
||||
Loading…
Reference in New Issue
Block a user