Skip to content

Harden cosmovisor migration for applied upgrade plans#379

Merged
p0mvn merged 1 commit into
mainfrom
fix/cosmovisor-applied-plan-migration
Jun 5, 2026
Merged

Harden cosmovisor migration for applied upgrade plans#379
p0mvn merged 1 commit into
mainfrom
fix/cosmovisor-applied-plan-migration

Conversation

@p0mvn

@p0mvn p0mvn commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Summary

  • read applied plan names from data/upgrade-info.json during direct->Cosmovisor migration and reject unsafe values
  • seed both cosmovisor/genesis/bin/svoted and cosmovisor/upgrades/<plan>/bin/svoted during migration when an applied plan exists
  • point cosmovisor/current at the applied plan path when present (fallback to genesis), and add focused regression coverage in scripts/test_chain_upgrade_runtime_mode.sh

Test plan

  • bash -n scripts/ci/ensure_cosmovisor_runtime.sh
  • bash -n scripts/test_chain_upgrade_runtime_mode.sh
  • bash scripts/test_chain_upgrade_runtime_mode.sh
  • gh workflow run "Deploy SDK" --ref fix/cosmovisor-applied-plan-migration -f tag=v1.0.2 -f target_environment=staging
  • gh run watch 27038177413 --exit-status
  • post-deploy checks:
    • curl -fsS https://stage.explorer-api.valargroup.org/shielded-vote/v1/rounds
    • curl -fsSI https://stage.snapshots.valargroup.org
    • read-only ssh checks for stage primary+secondary svoted service + cosmovisor runtime path

When direct-mode services migrate after a chain upgrade, seed both genesis and applied-plan runtime binaries from upgrade-info.json and point current at the applied plan to prevent missing upgrades/<plan>/bin/svoted regressions.
@p0mvn p0mvn merged commit 38cdca1 into main Jun 5, 2026
21 checks passed
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.

1 participant