base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify optional release diagnostics

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 17:14:15 +00:00
parent cd58b2bcfc
commit 54cfbd8eb8
2 changed files with 21 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/release.md
View File

@@ -73,9 +73,11 @@ The launcher builds the ReleaseKit version selected by the module in readonly
mode. After preflight, `publish` runs the offline default Go suite once, checks
the candidate and remote guards, creates an annotated tag from the committed
note, and pushes only that tag object. The launcher does not push `main`; push
the candidate first. Do not require a separate `check` before `publish` or repeat
the same suite. Successful source publication does not wait for CI, module
availability, or consumer installation.
the candidate first. `check` is available for optional diagnosis and is not a
required step before `publish`. The automated publication workflow runs the
final-candidate suite once; configured additional checks should avoid duplicating
that suite. Maintainers may rerun diagnostics when useful. Successful source
publication does not wait for CI, module availability, or consumer installation.
## Completion and statuses