Testnet 62: Iapetus

[conorsch]

Testnet Release

Testnet name: Iapetus
Release date: 2023-10-10
Testnet release manager: @conorsch

Testnet Release Manager Checklist

Preceding Friday (sprint planning day):

• Create GitHub project column, work with team to populate the milestone with tickets targeted for the release.

Tuesday (or after release of previous testnet):

• Construct the genesis data for the release: chore: update chain id for 062-iapetus #3124
  • Create new testnet directory with initial genesis allocations for this testnet by running cd testnets && ./new-testnet.sh
    • This genesis data will be used for testnet-preview with a randomized version of the future testnet's chain ID.

Thursday:

• Check in with team again in a release meeting and update the GitHub milestone to ensure it represents what will make it into the testnet.
• Draft an announcement for peer review to ensure major changes included are comprehensive.

Following Monday (release day):

• Verify that testnet-preview.penumbra.zone is operational; it is redeployed on every push to main, and is an exact preview of what is about to be deployed.
• 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.
• 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.
• You must manually review the Waiting deployment in the GitHub Actions UI before the deployment will begin. Monitor the GitHub action to ensure it completes after it is approved.
• Delegate to the Penumbra Labs CI validators; use amounts of ~200k penumbra per validator.
• Open a position to provide some initial liquidity: pcli tx lp replicate xyk penumbra:test_usd 20000penumbra --current-price 20
• Update CometBFT version in docs, cf. docs: revert to cometbft v034 for testnet docs #3134
• Reimport bot (Galileo & Osiris) seed phrases, for BIP44 update in https://discord.com/channels/824484045370818580/941008110473068545/1159959257735770142
• Update Galileo deployment, following docs.
• Update Osiris deployment, following docs.
• Make the announcement to Discord! 🎉🎉🎉

[conorsch]

Release has shipped. There were a few snags in the process, which I document here, for later follow-up:

• The mac & windows builds failed on the Release workflow: https://github.com/penumbra-zone/penumbra/actions/runs/6474718975/job/17580377131 hypothesis: potentially related to unix domain socket addition in tower-abci v0.10.0? build(pd): upgrade to tower-abci v0.10.0 #3142
• The new bot-update logic failed https://github.com/penumbra-zone/penumbra/actions/runs/6474719006/job/17580421735 due to an unescaped newline; easy fix.
• The Galileo and Osiris builds broke due to account_group_id -> wallet #3145, but the fix was super easy.
• I had to briefly allow pushing to main branch in the github repo to follow the cargo-release steps, which involve pushing a commit and tag. We cannot safely use this workflow with PRs unless we prohibit rebasing. Discuss with team.