Release process

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.

Was this useful?

On this page

Full release validation

Where each section moved

Molty