feat(backend): add contract upgrade path management#446
Open
Gezziy wants to merge 2 commits into
Open
Conversation
|
@Gezziy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #368
Summary
Adds backend support for contract upgrade path management, including:
Upgrade plan generation for contract version transitions
Semantic version validation
WASM hash change validation
Upgrade strategies for in-place, state migration, and redeploy-and-migrate flows
Compatibility check gating for storage layout, public interface, and authorization
Risk classification and approval requirements
Rollback plan generation
Security review summary in generated plans
POST /api/v1/contracts/upgrade-plan API endpoint
Unit and API-level tests for the upgrade planning flow
Reason
Implements issue #368 by adding a structured backend upgrade planning path for smart contracts. This gives reviewers and operators a deterministic way to assess upgrade readiness, risk, blockers, required approvals, and rollback steps before execution.