Skip to content

docs: document contract upgrade and migration process#458

Open
georgeefaith wants to merge 1 commit into
PrincessnJoy:mainfrom
georgeefaith:feat/331-upgrade-migration-docs
Open

docs: document contract upgrade and migration process#458
georgeefaith wants to merge 1 commit into
PrincessnJoy:mainfrom
georgeefaith:feat/331-upgrade-migration-docs

Conversation

@georgeefaith

Copy link
Copy Markdown

Closes #331

Summary

Expands docs/upgrade.md from a 13-line stub into a complete upgrade and migration guide.

Changes

  • docs/upgrade.md: full rewrite

What's documented

  • Step-by-step upgrade workflow (build → upload WASM → invoke upgrade → verify)
  • Admin requirements and multisig coordination
  • State migration: lazy migration for additive changes vs. explicit migrate entrypoint for breaking schema changes (with code example)
  • Rollback considerations: testnet-first, backups, pause window, re-upgrade with old hash
  • Upgrade checklist (pre/post steps)
  • Cross-references to rollback.md, admin-multisig-pattern.md, storage.md, runbook.md

@drips-wave

drips-wave Bot commented Jun 26, 2026

Copy link
Copy Markdown

@georgeefaith 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! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document contract upgrade and migration process

1 participant