-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish next Zebra release: 1.6.0 #7993
Closed
17 tasks
Comments
This was referenced Feb 21, 2024
7 tasks
7 tasks
@upbqdn can we add to the changelog(and maybe to the readme?) the minimal version of the protoc package needed to build Zebra. I have an older machine and i am getting the error:
|
Sure, I'll add it there. |
I opened #8315 instead. |
Merged
43 tasks
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
The text was updated successfully, but these errors were encountered: