fix
patch
task/fix-alembic-revision-collision
#1 / 1
fix: resolve Alembic revision ID collision in widen_auth_fingerprint migration
widen_auth_fingerprint_to_prefixed.py was generated with revision e5f6a7b8c9d0, which is already used by profile_snapshot_precompute.py. Alembic reported a cycle. Assigned a unique ID (a7b8c9d0e1f2) and chained it after the true head (e5f6a7b8c9d1 — rename_social_handle_to_social_url).
sha256:ebd38ab50e87c1da2dfc66c8a5354231348b8ea670e89cd2c1cd55654613812a
sha
sha256:b61c197709f9be668cd323dcf68fa8c6723974a59a3579db23131c4010b1fc2a
snapshot
← Older
Oldest on task/fix-alembic-revision-collision
All commits
Newer →
Latest on task/fix-alembic-revision-collision
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:ebd38ab50e87c1da2dfc66c8a5354231348b8ea670e89cd2c1cd55654613812a --body "your comment"
No comments yet. Be the first to start the discussion.