fix: remove false-positive proposal_comments index drop from migration 0072
The ix_proposal_comments_author_user_id index only existed on local (legacy name). Staging always had the correct ix_musehub_proposal_comments_author_user_id which is ORM-managed (index=True on column). Dropping it would break the ORM contract and the drop fails on staging anyway since the legacy name doesn't exist there.
sha256:a59da49c4611b970fc4b6ae48678ce4943261c213a07ddbd73ce9201df869b4a
sha
~2
symbols
1 changed · 973 in snapshot
files
sha256:e5ad33a73907d394f3a0800343700a81ed17215621b0d62780590baf6b139337
snapshot
~2
symbols modified
1
file changed
973
files in snapshot
0
dead code introduced
Semantic Changes
2 symbols
Files Changed
~1
973 in snapshot
~1
973 in snapshot
Older
Revert "fix: fetch/presign tip-only blob coverage + timing instr…
sha256:e449c773dc240750b3e081698c673c8f55da3d929c5d938fdb5d34b76d25480a
All commits
Newer
fix: unpack graph_map tuple with generation field
sha256:6701a95b67c336806e2a77503f3b1886a46bf895083fd6bed7c3645afdac60dc
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:a59da49c4611b970fc4b6ae48678ce4943261c213a07ddbd73ce9201df869b4a --body "your comment"
No comments yet. Be the first to start the discussion.