[ ] Start a manual workflow run with a Zebra and lightwalletd full sync.
State format changes can be made in zebra-state or zebra-chain. The state format can be changed by data that is sent to the state, data created within the state using zebra-chain, or serialization formats in zebra-state or zebra-chain.
After the test has been started, or if it has finished already:
[ ] Ask for a state code freeze in Slack. The freeze lasts until the release has been published.
Checkpoints
For performance and security, we want to update the Zebra checkpoints in every release.
Prepare for the Release
These release steps can be done a week before the release, in separate PRs. They can be skipped for urgent releases.
State Full Sync Test
To check consensus correctness, we want to test that the state format is valid after a full sync. (Format upgrades are tested in CI on each PR.)
lightwalletd
full sync.State format changes can be made in
zebra-state
orzebra-chain
. The state format can be changed by data that is sent to the state, data created within the state usingzebra-chain
, or serialization formats inzebra-state
orzebra-chain
.After the test has been started, or if it has finished already:
Checkpoints
For performance and security, we want to update the Zebra checkpoints in every release.
Missed Dependency Updates
Sometimes
dependabot
misses some dependency updates, or we accidentally turned them off.This step can be skipped if there is a large pending dependency upgrade. (For example, shared ECC crates.)
Here's how we make sure we got everything:
cargo update
on the latestmain
branch, and keep the outputdeny.toml
cargo update
to that PR as a commentPrepare and Publish the Release
Follow the steps in the release checklist to prepare the release:
Release PR:
Publish Release: