And I ran this from in your repo to take advantage of your superior knowledge of the AI. And I’m now vindicated in knowing that a team of experts can’t do any better than I am!
So, yeah, Claude, WHY NOT USE GENERATE MIGRATION!?!?!?
I changed the migration version in the database like this:
UPDATE schema_migrations
SET version = '20260319001231'
WHERE version = '20260319000001';
And renamed the migration in my plugin to match. That did the trick!
I’d blame myself for not pulling from discourse main as often as I should, but it was the same day, so even if I did it every day, it wouldn’t have helped. I guess I should pull from main and running migrations one more time before pushing, maybe. But I won’t let a migration like this happen again.
Thanks so much for your help. This was definitely a weird edge case that would never happen if we weren’t both using AI on the same day.