You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When planning release processes, parachain teams often bump into issues involving pallet-contracts migration and its compatibility with the downstream dependencies (i.e. cargo-contract and ink.
Therefore, it would be helpful both for the parachain teams and smart contract core team to establish a formal migration and compatibility guide.
After an upgrade, parachain teams can inform us of any problems and/or bugs during the process which we can note in the migration guide as well.
The text was updated successfully, but these errors were encountered:
Summary from the internal conversation
When planning release processes, parachain teams often bump into issues involving
pallet-contracts
migration and its compatibility with the downstream dependencies (i.e.cargo-contract
andink
.Therefore, it would be helpful both for the parachain teams and smart contract core team to establish a formal migration and compatibility guide.
After an upgrade, parachain teams can inform us of any problems and/or bugs during the process which we can note in the migration guide as well.
The text was updated successfully, but these errors were encountered: