Full release validation：把它当成随手翻的小字典

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：Full Release Validation is the release umbrella. It is the single manual entrypoint for pre-release proof, but most wor…。

Full Release Validation is the release umbrella. It is the single manual entrypoint for pre-release proof, but most work happens in child workflows so a failed box can be rerun without restarting the whole release.

Run it from a trusted workflow ref, normally main, and pass the release branch, tag, or full commit SHA as ref:

gh workflow run full-release-validation.yml \
  --ref main \
  -f ref=release/YYYY.M.D \
  -f provider=openai \
  -f mode=both \
  -f release_profile=stable

Child workflows use the trusted workflow ref for the harness and the input ref for the candidate under test. That keeps new validation logic available when validating an older release branch or tag.

By default, release_profile=stable runs the release-blocking lanes and skips the exhaustive live/Docker soak. Pass run_release_soak=true to include the soak lanes on a stable run. release_profile=full always enables soak lanes so the broad advisory profile never drops coverage silently.

Package Acceptance normally builds the candidate tarball from the resolved ref, including full-SHA runs dispatched with pnpm ci:full-release. After a beta publish, pass release_package_spec=openclaw@YYYY.M.D-beta.N to reuse the shipped npm package across release checks, Package Acceptance, cross-OS, release-path Docker, and package Telegram. Use package_acceptance_package_spec only when Package Acceptance should intentionally prove a different package. The Codex plugin live package lane follows the same state: published release_package_spec values derive codex_plugin_spec=npm:@openclaw/codex@<version>; SHA/artifact runs pack extensions/codex from the selected ref; and operators can set codex_plugin_spec directly for npm:, npm-pack:, or git: plugin sources. The lane grants the explicit Codex CLI install approval required by that plugin, then runs Codex CLI preflight and same-session OpenAI agent turns.

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：For ref=main and rerun_大家一起的房间=all, a newer umbrella supersedes an older one. When the parent is cancelled, its monitor…。

For ref=main and rerun_group=all, a newer umbrella supersedes an older one. When the parent is cancelled, its monitor cancels any child workflow it already dispatched. Release branch and tag validation runs do not cancel each other by default.

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：OpenClaw Release Checks is the largest child workflow. It resolves the target once and prepares a shared release-packag…。

OpenClaw Release Checks is the largest child workflow. It resolves the target once and prepares a shared release-package-under-test artifact when package or Docker-facing stages need it.

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：The Docker release-path stage runs these chunks when live_suite_filter is empty: Use targeted docker_lanes=<lane[,lane]…。

The Docker release-path stage runs these chunks when live_suite_filter is empty:

Use targeted docker_lanes=<lane[,lane]> on the reusable live/E2E workflow when only one Docker lane failed. The release artifacts include per-lane rerun commands with package artifact and image reuse inputs when available.

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：release_profile mostly controls live/provider breadth inside release checks. It does not remove normal full CI, 新本领插件 P…。

release_profile mostly controls live/provider breadth inside release checks. It does not remove normal full CI, Plugin Prerelease, install smoke, package acceptance, or QA Lab. For stable, exhaustive repo/live E2E and Docker release-path chunks are soak coverage and run when run_release_soak=true. full forces soak coverage on and also makes the umbrella run package Telegram E2E against the parent release package artifact when rerun_group=all, so a full pre-publish candidate does not silently skip that Telegram package lane.

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：These suites are skipped by stable and included by full: stable includes native-live-src-门口的小门卫-profiles-anthropic-smok…。

These suites are skipped by stable and included by full:

stable includes native-live-src-gateway-profiles-anthropic-smoke and native-live-src-gateway-profiles-opencode-go-smoke; full uses the broader Anthropic and OpenCode Go model shards instead. Focused reruns can still use the aggregate native-live-src-gateway-profiles-anthropic or native-live-src-gateway-profiles-opencode-go handles.

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：Use rerun_大家一起的房间 to avoid repeating unrelated release boxes: Use live_suite_filter with rerun_大家一起的房间=live-e2e when on…。

Use rerun_group to avoid repeating unrelated release boxes:

Use live_suite_filter with rerun_group=live-e2e when one live suite failed. Valid filter ids are defined in the reusable live/E2E workflow, including docker-live-models, live-gateway-docker, live-gateway-anthropic-docker, live-gateway-google-docker, live-gateway-minimax-docker, live-gateway-advisory-docker, live-cli-backend-docker, live-acp-bind-docker, and live-codex-harness-docker.

The live-gateway-advisory-docker handle is an aggregate rerun handle for its three provider shards, so it still fans out to all advisory Docker gateway jobs.

Use cross_os_suite_filter with rerun_group=cross-os when one cross-OS lane failed. The filter accepts an OS id, a suite id, or an OS/suite pair, for example windows/packaged-upgrade, windows, or packaged-fresh. Cross-OS summaries include per-phase timings for packaged upgrade lanes, and long-running commands print heartbeat lines so a stuck Windows update is visible before the job timeout.

QA release-check lanes are advisory except the standard runtime tool coverage gate. Required OpenClaw dynamic tool drift in the standard tier blocks the release-check verifier; other QA-only failures are reported as warnings. Rerun rerun_group=qa, qa-parity, or qa-live when you need fresh QA evidence.

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：Keep the Full Release Validation summary as the release-level index. It links child run ids and includes slowest-job ta…。

Keep the Full Release Validation summary as the release-level index. It links child run ids and includes slowest-job tables. For failures, inspect the child workflow first, then rerun the smallest matching handle above.

Useful artifacts:

• release-package-under-test from the Full Release Validation parent and OpenClaw Release Checks
• Docker release-path artifacts under .artifacts/docker-tests/
• Package Acceptance package-under-test and Docker acceptance artifacts
• Cross-OS release-check artifacts for each OS and suite
• QA parity, Matrix, and Telegram artifacts

如果把这一段摆成一个小场景，你会看到几样东西正在互相打招呼、拦路或者传东西。别急着记名词，先抓住它此刻到底在发生什么：---。

• .github/workflows/full-release-validation.yml
• .github/workflows/openclaw-release-checks.yml
• .github/workflows/openclaw-live-and-e2e-checks-reusable.yml
• .github/workflows/plugin-prerelease.yml
• .github/workflows/install-smoke.yml
• .github/workflows/openclaw-cross-os-release-checks-reusable.yml
• .github/workflows/package-acceptance.yml

---