Remove already applied pallet_multisig::migrations::v1::MigrateToV1 at humanode-runtime migrations scope

[dmitrylavrenov]

try-runtime checks at ci throw error now called Result::unwrap() on an Err value: Other("this migration can be deleted") after executed runtime upgrade at mainnet to 127 due to https://github.com/humanode-network/substrate/blob/8afcafd721d31939e4dee7b779f152ab9eb1c8be/frame/multisig/src/migrations.rs#L49

#1498 has faced this error. So, probably, we should remove it now.

Btw, I don't think that pallet_multisig::migrations should throw error for this logic at pre_upgrade implementation.

[MOZGIII]

This is actually interesting, and finally forces some pattern on the migrations management: remove them as soon as they're no longer useful.
This leads to some a set of complications and new things we have to keep an account for. Let's create an issue to discuss and think this through.

[dmitrylavrenov]

This is actually interesting, and finally forces some pattern on the migrations management: remove them as soon as they're no longer useful. This leads to some a set of complications and new things we have to keep an account for. Let's create an issue to discuss and think this through.

Yep, that's why the following rework was introduced - #1315 to unify the whole migrations scope.

[dmitrylavrenov]

This is actually interesting, and finally forces some pattern on the migrations management: remove them as soon as they're no longer useful. This leads to some a set of complications and new things we have to keep an account for. Let's create an issue to discuss and think this through.

#1500