🎁 [Feature Request]: Runtime Upgrade + Migrations for Ongoing Deployments

[4meta5]

templates

• [X] Generic Runtime Template
• [X] Evm Template

What is the feature you would like to see?

Current releases do not check backwards compatibility with deployments of the previous release. Best practices for new releases would check backwards compatibility and include migrations whenever necessary for all runtime upgrades.

• [ ] deploying a live testnet for each template
• [ ] upgrading the testnets from each old release to the new release to verify everything works as expected
• [ ] use try-runtime in the CI to verify backwards compatibility in this repo

Note that by backwards compatibility I actually mean that the code can execute the runtime upgrade in a way that does not corrupt storage or cause any other unexpected problems (i.e. changing extrinsic or pallet indices)

Contribution Guidelines

• [X] I agree to follow this project's Contribution Guidelines