Fix migration issue #1344
Merged
Fix migration issue #1344
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
shiki
approved these changes
Aug 12, 2019
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.
Fixes migration of
CHANGES_CONFIRMED_CONTENT_HASHCODEfield as it had a wrong type in the migration script.cc @loremattei This PR should fix the issue with migration in WPAndroid 13.1. However, I've fixed the migration script so the fix won't work for users who have already updated the app. But AFAIU WPAndroid 13.1 hasn't been released to anyone yet (not even to beta users), right?
Testing steps in WPAndroid
release/13.0release/13.1and update FluxC hash to5aa79629b12dabd24784548b8cf183bca458846b