Skip to content

No rollback procedure#210

Open
firstJOASH wants to merge 3 commits into
PrincessnJoy:mainfrom
firstJOASH:no-rollback-procedure
Open

No rollback procedure#210
firstJOASH wants to merge 3 commits into
PrincessnJoy:mainfrom
firstJOASH:no-rollback-procedure

Conversation

@firstJOASH
Copy link
Copy Markdown

Closes #98

- Add log() with timestamp and INFO/WARN/ERROR levels
- Tee all output to timestamped log file in logs/
- Add ERR trap reporting failing line number and log path
- Add explicit error handling with meaningful messages on all CLI calls
- Add check_required_env() that fails fast with clear error per missing var
- Add --check-env flag to validate env/toolchain without deploying
- Replace bare :? expansions with explicit check_required_env calls
- Add backup_contracts() to deploy.sh/deploy_mainnet.sh: saves contract IDs
  to logs/backups/contracts_{network}_{timestamp}.env before each deployment
- Add verify_deployment() that calls total_supply and get_proposal_count
  on deployed contracts before marking deployment complete
- Add scripts/rollback.sh: list backups, restore by file or --latest,
  update .env in-place, verify restored contracts on-chain
- Add docs/rollback.md documenting the full rollback procedure
@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented Jun 2, 2026

@firstJOASH 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.

No rollback procedure for failed deployments

1 participant