implement NoOpMigration for 0.30.0-alpha #6535
Merged
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.
We tried to release version 0.30.0-alpha of Airbyte without any Migration for version 0.30.0-alpha but the deployment started failing. This is because we rely on Automatic migration to make the database version with the new version value here
But the fact that we didnt introduce any migration, the automatic migration failed saying no migration found for version 0.30.0-alpha.
Because of that the db version was not updated with the new incoming version and as a result the check
AirbyteVersion.isCompatible(airbyteVersion, airbyteDatabaseVersion.get())
here failed and the server didnt start up.In order to solve it we introduced a NoOpMigration and tested it locally and it worked