Release Testnet 74, deimos-7, via chain upgrade

[conorsch]

Testnet Release

Testnet name: Testnet 74, penumbra-testnet-deimos-7, with chain upgrade
Release date: 2024-05-09
Testnet release manager: @conorsch

Testnet Release Manager Checklist

We intend to ship a chain upgrade to the current testnet, including all the changes queued up in main. We must ensure that all necessary migrations have been written and tested.

Pre-release:

• Review all merged PRs with tags consensus-breaking and/or state-breaking
• Confirm migrations exist where required for breaking changes already merged
• Identify specific test cases for before/after behavior, querying chain state, to ensure that migrations are effective
• (Stretch goal): Land automated upgrade testing as described in ci: automated testing of migration compatibility #4323
• Land 11th hour PRs:
  • penumbra: use core.auction.v1 #4368
  • chore: bump app version 2 -> 3 #4367
  • auction(vcb): add a value circuit breaker #4363
  • IncludeDelegatorVoteView as an ActionView with Visible and Opaque Variants #4291

On release day:

• Draft an announcement for peer review to ensure major changes included are comprehensive.
• Disable testnet deploy workflow, so that chain is not reset
• Bump the version number and push its tag, via cargo-release.
  • Run cargo release minor for a new testnet, or cargo release patch for a bugfix. For the latter, make sure you're on a dedicated release branch.
  • Push the commit and newly generated tag, e.g. v0.51.0, to the remote.
• Manually trigger container-build workflow, bc deploy workflow is disabled
• Wait for the "Release" workflow to complete: it'll take ~60m, most of which is the Windows builds.
• Edit the newly created (and published) release object, then click "Generate release notes." Cut and paste the generated text from the bottom to the top of the post, then save it.
• Close faucet (chain halt will make it inoperative anyway)
• Run migrations on all validators
• Run migrations on all fullnodes
• Update Galileo deployment, following docs.
• Make the announcement to Discord! 🎉🎉🎉

Post-release cleanup tasks

• Ensure faucet is open
• Perform Hermes maintenance to get relayer running again
• Update GH templates for:
  • release planning (this template was heavily revised and can be reused)
  • PR templates to ask for test plans

[conorsch]

Testnet 74 migration was mishandled, due to TOTAL_CHAIN_HALT not being reset during 73 release. We're now prioritizing a chain reset as Testnet 75, in #4374.