Skip to content
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

Define storage migrations required to upgrade from Polkadot 0.9.42 to 1.1.0 #482

Open
gianfra-t opened this issue May 29, 2024 · 0 comments

Comments

@gianfra-t
Copy link
Contributor

Context

As part of the overall task of updating to Polkadot 1.1.0 (see tasks/#306) we need to identify which migrations need to be defined manually and added to the runtime before performing the upgrade, such that the on-chain storage versions are updated as well.

Migrations that need to be specified manually are to be defined in the runtime here, where the migration function should be defined on the corresponding pallet.

Steps

We can start by using the general information found here regarding storage version management of the pallets. We should not have any discrepancy between the on-chain version and the version the code specifies at the moment.

Ideally, the process should be:

  • For each pallet:
    • Identify the current storage version.
    • Identify the version that polkadot-v1.1.0 uses.
    • Check if the pallet defines a migration automatically or needs to be specified manually.
    • If it doesn't specify automatically, identify which migration functions must be called (could be more than one)

The migration code should be added to the modifications done in this ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant