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
This could be a preflight check to ensure that there is some basic level of compliance with Cadence V1.0 update rules before somebody stages to the network. It could prevent friction where developers stage contracts, later find out from external analysis that this is invalid, have to repeat process. The idea is to catch obvious errors where somebody makes an incompatible update.
Instructions
Please fill out the template below to the best of your ability.
Issue To Be Solved
We should add the cadence 1.0 update checker to the staging contracts command.
This could be a preflight check to ensure that there is some basic level of compliance with Cadence V1.0 update rules before somebody stages to the network. It could prevent friction where developers stage contracts, later find out from external analysis that this is invalid, have to repeat process. The idea is to catch obvious errors where somebody makes an incompatible update.
(see https://discordapp.com/channels/613813861610684416/1108479699732152503/1217869683030622352)
(Optional): Suggest A Solution
Add this check but make it optional. It should not block users from staging entirely as outlined in Discord.
The text was updated successfully, but these errors were encountered: