Closed sisyphusSmiling closed 4 months ago
Update: As of this writing, MigrationStagingContract
migrated successfully in a local migration and has been staged for inclusion in the subsequent Testnet migration.
Attention: Patch coverage is 93.44262%
with 4 lines
in your changes missing coverage. Please review.
Please upload report for BASE (
stable-cadence@735a84b
). Learn more about missing BASE report.
Files | Patch % | Lines |
---|---|---|
contracts/DependencyAudit.cdc | 93.02% | 3 Missing :warning: |
.../staged-contract-updates/StagedContractUpdates.cdc | 87.50% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Related: #1
This PR updates repo contents for Cadence 1.0 compatibility. While the
MigrationStagingContract
won't be used after 1.0 migration, staging and updating the contract will enhance auditability and transparency post-migration, enabling the migrated contracts can be validated against the code as staged. Migrating the contract also allows us to clean up the account after some time if need be.Refactors for
StagedContractUpdates
are also included. Although this contract was not used as a mechanism for migration as originally intended, others may still find it useful moving forward to coordinate updates to distributed contract system.