You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [ ] Version bumps match user-visible changes for each crate (`major` for network upgrades or breaking API, `minor` for new API/behavior/RPC/config, `patch` otherwise)
34
-
- [ ] Each changed crate's `[Unreleased]` entries follow the Changelog Guidelines (operator-focused in the root `CHANGELOG.md`, crate-consumer-focused per crate)
35
-
- [ ] `[Unreleased]` has been renamed to the release heading (`## [Zebra <version>]` in the root, `## [<version>]` per crate)
36
-
- [ ] No git dependencies remain in crates publishing to crates.io (`check-no-git-dependencies`)
37
-
- [ ] Any required checkpoint, end-of-support height, README, or operational changes already landed
38
-
- [ ] `RELEASE_APP_ID` and `RELEASE_APP_PRIVATE_KEY` are configured at repository or organization scope
39
-
- [ ] Merge only when crates should publish and the public `zebrad` GitHub Release should be created
40
-
41
-
## Release Summary
31
+
## Release summary
42
32
43
33
{% for release in releases %}
44
-
- `{{ release.package }}`: {% if release.previous_version and release.previous_version != release.next_version %}{{ release.previous_version }} -> {% endif %}{{ release.next_version }}
34
+
- `{{ release.package }}`: {% if release.previous_version and release.previous_version != release.next_version %}{{ release.previous_version }} → {% endif %}{{ release.next_version }}
45
35
{%- endfor %}
46
36
37
+
## Review this release
38
+
39
+
Review the latest commit after all intended changes have landed on `main` and release-plz has finished updating this PR.
40
+
41
+
### Release prerequisites
42
+
43
+
- [ ] No unintended prerelease dependency versions remain.
44
+
45
+
For releases that include `zebrad`:
46
+
47
+
- [ ] A full sync completed after the latest state change, or no new full sync is required.
48
+
- [ ] Mainnet and Testnet checkpoints are current for this release.
49
+
50
+
### Release contents
51
+
52
+
- [ ] If `zebrad` is included, the root changelog covers every operator-visible change since the previous `zebrad` release.
53
+
- [ ] Each crate changelog covers every consumer-visible change since that crate's previous release.
54
+
- [ ] Changelog entries describe the final behavior, use the correct category, and link the relevant pull requests.
55
+
56
+
### Versions
57
+
58
+
- [ ] If `zebrad` is included, its proposed version follows the release policy, and its stable or prerelease status is correct.
59
+
- [ ] Each crate version follows Cargo SemVer for its API and behavior changes, and dependency-only releases use the smallest required bump.
60
+
- [ ] Every release heading matches the corresponding version in the release summary.
61
+
62
+
### Release data and documentation
63
+
64
+
For releases that include `zebrad`:
65
+
66
+
- [ ] The end-of-support height matches the intended release date.
67
+
- [ ] Network-upgrade activation heights and the minimum network protocol version are correct, when applicable.
68
+
- [ ] README, installation, compatibility, and operational documentation match the release.
69
+
70
+
### Approval
71
+
72
+
- [ ] This exact commit is ready to publish.
73
+
74
+
Merging this PR publishes the listed crates and creates their git tags. If `zebrad` is listed, the workflow also creates the public GitHub Release and starts the binary, Docker, and GCP release workflows.
75
+
47
76
---
48
77
This PR was generated with [release-plz](https://github.com/release-plz/release-plz/).
Copy file name to clipboardExpand all lines: book/src/dev/release-process.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,13 +128,12 @@ To help ensure that you have sufficient time and a clear path to update, this is
128
128
129
129
## Release candidate & release process
130
130
131
-
Stable releases are generated from `main` by `release-plz`.
132
-
After each push to `main`, release-plz opens or updates a Release PR when it finds releasable crate changes.
133
-
The generated Release PR contains version bumps and changelog updates for the crates that changed.
134
-
The Release PR is the manual review gate: after maintainers review and merge it, the release workflow publishes crates to crates.io, creates the release git tags, and creates the public `zebrad` GitHub Release.
131
+
Releases are generated from `main` by `release-plz`. After each push to `main`, release-plz opens or updates a Release PR when it finds releasable crate changes. The generated PR contains the proposed version bumps and a summary of the crates to publish; when it includes `zebrad`, the PR title identifies the proposed `zebrad` version.
132
+
133
+
The Release PR is the manual review gate. After maintainers review and merge it, the release workflow publishes crates to crates.io, creates the release git tags, and creates the public `zebrad` GitHub Release.
135
134
136
135
The `zebrad` GitHub Release triggers the downstream release workflows that build and publish signed Docker images, attach signed, checksummed standalone `zebrad` binaries (Linux `x86_64` and `aarch64`) to the GitHub Release, and deploy long-lived GCP nodes.
137
-
Until release-preparation data is automated, any required checkpoint, end-of-support height, README, or operational release-note changes should land on `main` before the generated Release PR is merged.
136
+
Changelogs are authored in source PRs rather than generated by release-plz. Final release headings and any required checkpoint, end-of-support height, README, or operational release-note changes must land on `main` before maintainers approve the generated Release PR.
138
137
139
138
release-plz embeds the release checklist in the generated Release PR body using the `pr_body` configured in `.release-plz.toml`.
140
139
GitHub pull request templates are only used when a maintainer manually opens a pull request in the GitHub UI.
0 commit comments