I don't understand how to update the store through migrations

[valli0x]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

If the current commit version and the update height do not match when starting the node, then there will be no update of the store?
Do I need to launch the application before the block that has a planned update?

cosmos-sdk/simapp/upgrades.go

Line 56 in 3c9fa96

app.SetStoreLoader(upgradetypes.UpgradeStoreLoader(upgradeInfo.Height, &storeUpgrades))

cosmos-sdk/x/upgrade/types/storeloader.go

Line 14 in 3c9fa96

if upgradeHeight == ms.LastCommitID().Version+1 {

Cosmos SDK Version

0.50.x

How to reproduce?

No response

[tac0turtle]

If the current commit version and the update height do not match when starting the node, then there will be no update of the store? Do I need to launch the application before the block that has a planned update?

correct if you stop and start the node with the updated binary the node will not be able to start. If you would like to run migrations the module itself needs to specify the migration and in the module.go it will register the migrations that need to be run at the upgrade height.

Ill close this issue for now, but please ask further questions if you need

[valli0x]

@tac0turtle I mean, migrations for the store are not checked in the preblock upgrade of the module and are launched at the start of the node
The condition is that the launch should start at a height determined by a height in plan, so immediately upon node startup, it should start at the height of the plan block.

cosmos-sdk/x/upgrade/types/storeloader.go

Line 14 in 3c9fa96

if upgradeHeight == ms.LastCommitID().Version+1 {