Conversation
|
Need to check HeaderMMR pallet storage name, if dependency is using new frame v2 darwinia/runtime/crab/src/lib.rs Line 192 in 711c8c5 Might be |
hackfisher
left a comment
hackfisher
left a comment
There was a problem hiding this comment.
Due to the changes in darwinia-network/darwinia-common#673 and
This darwinia-common companion and maybe also migration need to be upgraded.
Need carefully review considering the changes in darwinia-v0.10.1
hackfisher
left a comment
hackfisher
left a comment
There was a problem hiding this comment.
Current base branch master is using the deprecate commit darwinia-network/darwinia-common@4e2a5df before mmr patch.
After the runtimes in v0.10.1 be applied, the dependency will require to be changed to commit after mmr patch(using new header mmr pallet).
https://github.com/darwinia-network/substrate-update-tracking/issues/19
If we use commits after darwinia-v0.11.1, check the migration differences between these substrate version(companion polkadot can be used as reference).
|
darwinia-common dependency reference: darwinia-network/darwinia-common@darwinia-v0.10.0...darwinia-v0.10.1 |
|
Related polkadot release with same substrate dependency: https://github.com/paritytech/polkadot/releases/tag/v0.9.0 What's the changes cause the mandatary upgrade for the nodes? The new host function mentioned in polkadot v0.9.0? Any related pull request links to this break changes? |
The test result show like this: #662 (comment) |
|
Already linked in CHANGELOG |
Co-authored-by: HackFisher <hackfisher@gmail.com>
3 participants
No description provided.