Peter Steinberger
c93c3e0b55
Live, Docker, channel and release wrappers could repeat failed validation or downgrade failed jobs automatically. Run each test invocation once, remove known-flake redispatch, and require an explicit recorded waiver when the release policy permits one. Wait for the original plugin publisher to settle before reporting failure. Keep bounded artifact-download recovery before tests. Read published v2026.9.6 empty retry metadata without restoring executable allowances or automatic waivers, preserving the sealed plan digest. Use the existing fresh-read owner for release-priority cleanup. Testbox owner/sibling proof and three CI-config replays passed. The two freshness regressions passed 20 repetitions. Published evidence retained its original digest; nonempty retry metadata remained rejected. The stale Testbox assertion now matches its already-landed four-hour lease; this change raises no runtime, test, hook or watchdog budget.
4.7 KiB
doc-schema-version, summary, title, read_when
| doc-schema-version | summary | title | read_when | |||
|---|---|---|---|---|---|---|
| 1 | Index of the Full Release Validation reference, one page per reader job | Full release validation |
|
Full Release Validation is the release product-validation umbrella. Most work
happens in child workflows so a failed box can be rerun without restarting the
whole release.
Test failures remain failures. Full Release Validation never automatically reruns failed or timed out jobs. Diagnose the original failure before using an explicit operator recovery command.
This page is an index. The reference is documented on seven pages, one per reader job. Open the page that matches your task and complete that validation pass there.
For a frozen target, declare exact test omissions in the initial request; see exact frozen-target test omissions. The Node and extension inputs validate the selected inventory and remain bound to the immutable coverage identity.
| Page | Read it when |
|---|---|
| Dispatch a validation run | Starting a run: Code SHA, Tooling SHA, helper inputs, and the immutable execution plan. |
| Continue a failed validation | Rerunning one job or failed children on an existing parent, and the post-merge continuation proof. |
| Extended-stable and changelog-only validation | Extended-stable dispatch, changelog-only reuse, coverage policies, and Telegram waivers. |
| Top-level stages | The umbrella stage matrix, evidence reuse, artifact producers, and decision states. |
| Release checks stages | The OpenClaw Release Checks stage matrix and the Docker release-path chunks. |
| Release profiles and focused reruns | Comparing profile coverage and picking a focused rerun_group or suite filter. |
| Evidence to keep | Recording evidence after a pass, and the backing workflow files. |
Where each section moved
Every section heading from the previous single-page version keeps its anchor
here, so an existing link such as
/reference/full-release-validation#post-merge-continuation-proof still
resolves. Each entry points at the page that now holds the content.
- Continue failed child jobs
- Post-merge continuation proof
- Extended-stable validation
- Top-level stages
- Release checks stages
- Docker release-path chunks
- Release profiles
- Full-only additions
- Focused reruns
- Evidence to keep
- Workflow files