Change the database migration CI workflow to check for the expected DB version instead #2250
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…B version instead Instead of checking for the expected tables which might come and go, make sure that the version corresponds to the highest version in the database migration files.
rdimitrov
approved these changes
Feb 1, 2024
JAORMX
approved these changes
Feb 1, 2024
|
let's hold merging this, I'll try if the CI fix works by dropping a table |
actually nah, the local tests seem to work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of checking for the expected tables which might come and go,
make sure that the version corresponds to the highest version in the
database migration files.