Add storage migration for Operator struct change and bump runtime version
#3342
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
Signed-off-by: linning <linningde25@gmail.com>
Signed-off-by: linning <linningde25@gmail.com>
vedhavyas
approved these changes
Jan 10, 2025
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.
#3279 removed a field from
Operatorstruct but lack of storage migration, unfortunately. This caused issue on Taurus as the last runtime upgrade brought that change to the Taurus network. Mainnet is not affected since domain is not enabled there.This PR adds the missing storage migration for the
Operatorstorage and bumps the runtime version. I have simulated the issue in a local network and verified the fix does work as expected.NOTE: this PR targets the
taurus-runtime-upgradebranch (which is where the last runtime upgrade was built from) notmain, because the issue only affects Taurus and the migration is one-off usage, doing so we don't need to worry about forgetting to delete the migration code and affect runtime upgrade in Mainnet in the future.Code contributor checklist: