fix(indexer): bump warbow_revenge_window migration timestamp to resolve PK collision (GitLab #150)
closes #150 (closed).
two migrations independently chose version 20260504200000:
20260504200000_doub_vesting_rescue_erc20(#137 (closed))20260504200000_warbow_revenge_window_gl135(#135 (closed))
sqlx primary-keys _sqlx_migrations on version. first applies fine, second collides on PK and the indexer cannot bootstrap on a clean DB at HEAD 16deec2.
bumps the warbow_revenge_window pair to 20260504201000 so both migrations apply ordered:
20260504200000_doub_vesting_rescue_erc20.{up,down}.sql (unchanged)
20260504201000_warbow_revenge_window_gl135.{up,down}.sql (renamed)content of either migration is untouched — pure rename. since neither migration has been run on prod yet (this is a pre-mainnet TGE window), no down-migration / re-apply required for existing envs.
repro before fix:
docker exec yieldomega-pg psql -U yieldomega -d postgres -c "DROP DATABASE IF EXISTS yieldomega_indexer;"
docker exec yieldomega-pg psql -U yieldomega -d postgres -c "CREATE DATABASE yieldomega_indexer OWNER yieldomega;"
cd indexer && cargo run --release
# fails on 'duplicate key value violates unique constraint _sqlx_migrations_pkey'after fix: clean bootstrap. once merged, will pull on QA server, bring up stack, walk #144 (closed) live.