-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix message update migration not applying #1164
Conversation
feel free to merge directly @mishig25 |
@@ -150,7 +150,7 @@ const updateMessageUpdates: Migration = { | |||
_id: new ObjectId("5f9f4f4f4f4f4f4f4f4f4f4f"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't we have to change the id?
Otherwise, since migration with this id was already recorded as done, it will not run. No?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or should we create new migration src/lib/migrations/routines/06-xyz.ts
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the idea was to delete the existing migration flag in the prod db so it would run again. But I think migrations should be append only no? Not sure how we could squash them together effectively
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah good call, updated the id so it will run again. The first run didn't work so this should be safe
* fix: message update migration not applying * feat: change message updates migration id to trigger re-run
Fixes the message update migrations needed as part of #996 not applying to the tools objects.