-
Notifications
You must be signed in to change notification settings - Fork 14
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
Update runtimes to polkadot-v0.9.40
#219
Comments
Hey team! Please add your planning poker estimate with Zenhub @ashneverdawn @ebma @RustNinja @TorstenStueber |
Maybe it makes sense to even switch to Polkadot version 0.9.40 now – it is already supported by orml. This would also require a follow up task to not just execute the runtime upgrade but first to redeploy all of our collator nodes. |
Sure, we'd just need to double-check the |
polkadot-v0.9.38
polkadot-v0.9.40
I created a |
For that reason I want to re-estimate. @vadaynujra is such a feature not available (change an estimate)? |
@TorstenStueber including https://github.com/pendulum-chain/spacewalk, right? |
Yes I would think this will be higher than 3. The jump from .37 to .40 is huge. A few changes I found:
And there's plenty more. |
8 would be fine. |
Alright, done. |
Hello, will this include |
@Curu24 Is this a new feature introduced in Substrate recently? Can you refer to it please? |
|
Since this feature has been merged already many months ago, it is already included in the So, it looks to me like the Pendulum nodes would already include this functionality even without this PR. |
Oh, yes, sorry. You're right. I was trying with the older release 0.9.29. With 0.9.37 it works. |
We should update our runtime dependencies to version
polkadot-v0.9.38
so that we get rid of some dependency conflicts.For example, we were running into problems because our spacewalk pallets use
jsonrpsee
with version >0.16.0 but other parachain pallets that are onpolkadot-v0.9.37
still usejsonrpsee
version 0.15.x (e.g. Zenlink) which then leads to conflicts when importing RPC modules from their pallets.The text was updated successfully, but these errors were encountered: