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

im-online session keys migration will not run on Kusama #262

Closed
s0me0ne-unkn0wn opened this issue Mar 29, 2024 · 3 comments · Fixed by #263
Closed

im-online session keys migration will not run on Kusama #262

s0me0ne-unkn0wn opened this issue Mar 29, 2024 · 3 comments · Fixed by #263

Comments

@s0me0ne-unkn0wn
Copy link
Contributor

We have a Kusama runtime upgrade to 1.1.3 on track that will be enacted soon: https://kusama.subsquare.io/referenda/359

That will prevent the execution of the session keys migration in 1.2.0 release:

const UPGRADE_SESSION_KEYS_FROM_SPEC: u32 = 1001002;

CC @bkchr

@bkchr
Copy link
Contributor

bkchr commented Mar 29, 2024

Good find. Can you please make a pr to fix this? Then we need to revert the release once more 🙈

@s0me0ne-unkn0wn
Copy link
Contributor Author

Can you please make a pr to fix this?

Sure. The question is, do I need to fix it for Polkadot as well? I'm not sure if the Polkadot upgrade pipeline strictly follows Kusama's one. Like, if we have 1.1.2 -> 1.1.3 -> 1.2.0 on Kusama, is it exactly the same for Polkadot? (I mean in the best-case scenario when OpenGov approves those changes)

@bkchr
Copy link
Contributor

bkchr commented Mar 29, 2024

The upgrade will also be applied for polkadot https://polkadot.polkassembly.io/referenda/581

bkchr pushed a commit that referenced this issue Mar 29, 2024
Fixes #262

CC @bkchr 

- [x] Does not require a CHANGELOG entry
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

Successfully merging a pull request may close this issue.

2 participants