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
No human pushes tags or updates `stable`/`beta` directly, the CI handles everything after the PR merges.
20
+
21
+
## Cutting a release candidate
22
+
23
+
1. Create a branch named `release/vX.Y.Z-rc1`. For the first RC of a new version, bump the version in `Cargo.toml` and run `cargo check` to update `Cargo.lock`. Always update `CHANGELOG.md`.
24
+
2. Open a PR targeting `main`. Get two approvals and merge.
25
+
3. CI creates the tag, fast-forwards `beta`, builds and signs binaries, Docker images, and creates a draft release on GitHub.
26
+
4. Test the RC on testnets. For subsequent RCs (`-rc2`, etc.), open a new release PR with only a `CHANGELOG.md` update (`Cargo.toml` does not change between RCs).
27
+
28
+
## Cutting the full release
29
+
30
+
Once testing is complete and signoffs are collected:
31
+
32
+
1. Create a branch named `release/vX.Y.Z` and update `CHANGELOG.md` with final release notes.
33
+
2. Open a PR targeting `main`. Get two approvals and merge.
34
+
3. CI creates the tag, fast-forwards `stable`, builds and signs artifacts, and creates a draft release.
35
+
4. Open the draft release on GitHub:
36
+
- Click **Generate release notes** and add a plain-language summary at the top
37
+
- Call out any breaking config changes explicitly
38
+
- Insert the [binary verification boilerplate text](#verifying-release-artifacts)
39
+
- Set as **latest release** (not pre-release)
40
+
- Publish
41
+
5. Update the community.
42
+
43
+
## If the pipeline fails
44
+
45
+
CI will automatically delete the tag if any build step fails. `stable` and `beta` are only updated after all artifacts are successfully built, they are never touched on a failed run. Fix the issue and open a new release PR.
46
+
47
+
## Verifying release artifacts
48
+
49
+
All binaries are signed using [Sigstore cosign](https://docs.sigstore.dev/about/overview/). You can verify any binary was built by the official Commit-Boost CI pipeline from this release's commit.
0 commit comments