ci: fold parity into QA release validation by vincentkoc · Pull Request #74622 · openclaw/openclaw

vincentkoc · 2026-04-29T21:10:53Z

Summary

remove the standalone Parity gate workflow entirely
keep the parity run nested in the existing QA-Lab - All Lanes mock parity lane and release-checks QA parity group
point docs at Full Release Validation with rerun_group=qa-parity / release-checks QA coverage instead of PR landing CI
rename remaining parity job/docs wording away from standalone gate language

Testing

git diff --check
go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.11 .github/workflows/qa-live-transports-convex.yml .github/workflows/openclaw-release-checks.yml .github/workflows/full-release-validation.yml
python3 scripts/check-composite-action-input-interpolation.py
node scripts/check-no-conflict-markers.mjs
pnpm exec oxfmt --check --threads=1 docs/ci.md docs/help/testing.md docs/reference/RELEASING.md docs/concepts/qa-e2e-automation.md .github/workflows/qa-live-transports-convex.yml
pnpm docs:check-mdx

vincentkoc · 2026-05-01T11:58:28Z

/clawsweeper automerge

clawsweeper · 2026-05-01T11:59:44Z

Codex review: passed.

Summary
The PR deletes the standalone Parity gate workflow, renames QA parity wording from gate to lane, routes docs toward QA/release validation, and adjusts the Docker E2E boundary guard for package-backed live lanes.

Reproducibility: not applicable. as a CI/docs refactor. The high-confidence review path is static comparison of the repaired PR diff against current workflow/docs code plus exact-head check status.

Next step before merge
No repair lane is needed; review findings are empty and exact-head checks/mergeability should gate the automerge path.

Security
Cleared: The diff deletes one workflow and edits docs/job labels plus a validation guard; it does not add actions, dependencies, permissions, secrets, downloads, or new code-execution paths.

Review details

Best possible solution:

Land the repaired consolidation through the automerge path once exact-head checks and branch protection pass, keeping parity coverage in QA-Lab and release-validation entrypoints.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a CI/docs refactor. The high-confidence review path is static comparison of the repaired PR diff against current workflow/docs code plus exact-head check status.

Is this the best way to solve the issue?

Yes, after the repair. The patch removes duplicated standalone parity workflow routing while preserving QA parity in existing QA/release validation and aligning the Docker guard with current package-backed live lanes.

What I checked:

Protected automerge PR: The GitHub API and provided context show this PR is open at head 3482654 with maintainer and clawsweeper:automerge labels, so it should stay open for review/automerge gating rather than cleanup close. (34826540587c)
Diff matches requested consolidation: The repaired diff removes .github/workflows/parity-gate.yml and changes QA parity wording in workflows/docs from standalone gate language to lane/release-validation language. (.github/workflows/parity-gate.yml:1, 34826540587c)
Release checks already own QA parity lanes: Current main exposes qa-parity as a release-check rerun group and runs candidate/baseline QA Lab parity lanes plus a parity report. (.github/workflows/openclaw-release-checks.yml:515, 9eb79bcf997b)
Full Release Validation routes qa-parity: Current main includes qa-parity in Full Release Validation inputs and dispatches release checks for that rerun group. (.github/workflows/full-release-validation.yml:53, 9eb79bcf997b)
Existing public docs support the new routing: The full release validation reference already documents QA parity as direct release-check jobs with rerun_group=qa-parity or rerun_group=qa. Public docs: docs/reference/full-release-validation.md. (docs/reference/full-release-validation.md:67, 9eb79bcf997b)
Prior docs regression is repaired: The repaired diff no longer removes install-smoke Docker coverage, and current docs still list root Docker image reuse, QR package install, Docker smokes, installer Docker tests, Bun smoke, and bundled-plugin E2E. Public docs: docs/reference/full-release-validation.md. (docs/reference/full-release-validation.md:62, 9eb79bcf997b)

Likely related people:

steipete: Recent available history on the central release workflow/docs and Docker E2E planning surfaces is dominated by Peter Steinberger commits, including release baseline expansion and the package-backed Codex npm plugin Docker live proof that motivates the guard adjustment. (role: recent maintainer; confidence: high; commits: 4b4dfe429d, 5c15ce3476, 23ac9ccfd5; files: .github/workflows/openclaw-release-checks.yml, .github/workflows/full-release-validation.yml, docs/ci.md)

Remaining risk / open question:

One exact-head check was still in progress at review time, so merge should wait for required checks and mergeability to finish green.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 9eb79bcf997b.

clawsweeper · 2026-05-01T12:02:29Z

🦞🦞
ClawSweeper automerge is enabled.

Head: 34826540587c
Label: clawsweeper:automerge
Action: exact-head review queued.
Flow: review this head, repair/rebase only if needed, then re-review the exact repaired head before merge.

Draft PRs stay fix-only until GitHub marks them ready for review. Pause with /clawsweeper stop.

Automerge progress:

2026-05-02 19:36:47 UTC review queued [`228a2c24507e`](https://github.com/openclaw/openclaw/commit/228a2c24507e68fbc1c621dbe720468719c67656) (queued)
2026-05-02 19:40:37 UTC review requested repair [`228a2c24507e`](https://github.com/openclaw/openclaw/commit/228a2c24507e68fbc1c621dbe720468719c67656) (structured ClawSweeper marker: fix-required (finding=review-feedback sha=228a2c...)
2026-05-01 12:05:46 UTC repair queued `228a2c24507e` (autonomous) Run: https://github.com/openclaw/clawsweeper/actions/runs/25213672556
2026-05-01 12:38:00 UTC repair queued `228a2c24507e` (autonomous) Run: https://github.com/openclaw/clawsweeper/actions/runs/25214527123
2026-05-01 12:40:24 UTC repair queued `228a2c24507e` (autonomous) Run: https://github.com/openclaw/clawsweeper/actions/runs/25214595691
2026-05-02 19:33:12 UTC review queued [`228a2c24507e`](https://github.com/openclaw/openclaw/commit/228a2c24507e68fbc1c621dbe720468719c67656) (queued)
2026-05-02 19:40:53 UTC repair queued [`228a2c24507e`](https://github.com/openclaw/openclaw/commit/228a2c24507e68fbc1c621dbe720468719c67656) (autonomous) Run: https://github.com/openclaw/clawsweeper/actions/runs/25260206461
2026-05-02 19:53:26 UTC repair completed [`34826540587c`](https://github.com/openclaw/openclaw/commit/34826540587c386907c00ad2d243c04bb4be60e8) (branch updated) in 9m 57s Run: https://github.com/openclaw/clawsweeper/actions/runs/25260206461 initial automerge rebase is delegated to Codex repair
2026-05-02 19:53:25 UTC review queued [`34826540587c`](https://github.com/openclaw/openclaw/commit/34826540587c386907c00ad2d243c04bb4be60e8) (after repair)
2026-05-02 19:57:16 UTC review queued [`34826540587c`](https://github.com/openclaw/openclaw/commit/34826540587c386907c00ad2d243c04bb4be60e8) (queued)
2026-05-02 19:57:04 UTC review passed [`34826540587c`](https://github.com/openclaw/openclaw/commit/34826540587c386907c00ad2d243c04bb4be60e8) (structured ClawSweeper verdict: pass (sha=34826540587c386907c00ad2d243c04bb4be6...)
2026-05-02 19:57:17 UTC merged [`34826540587c`](https://github.com/openclaw/openclaw/commit/34826540587c386907c00ad2d243c04bb4be60e8) (merged by ClawSweeper automerge)
2026-05-02 19:57:20 UTC review queued [`34826540587c`](https://github.com/openclaw/openclaw/commit/34826540587c386907c00ad2d243c04bb4be60e8) (queued)

Summary: - The PR deletes the standalone `Parity gate` workflow, renames QA parity wording from gate to lane, routes docs toward QA/release validation, and adjusts the Docker E2E boundary guard for package-backed live lanes. - Reproducibility: not applicable. as a CI/docs refactor. The high-confidence review path is static comparison of the repaired PR diff against current workflow/docs code plus exact-head check status. ClawSweeper fixups: - Included follow-up commit: ci: fold parity into QA release validation - Ran the ClawSweeper repair loop before final review. Validation: - ClawSweeper review passed for head 3482654. - Required merge gates passed before the squash merge. Prepared head SHA: 3482654 Review: openclaw#74622 (comment) Co-authored-by: Vincent Koc <vincentkoc@ieee.org> Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>

…approval-turn-tool-followthrough timeouts Carries forward the surface-bump portion of #74290 (closed in favor of this slim follow-up since the parity-gate.yml workflow file the original PR also touched was retired by #74622 'ci: fold parity into QA release validation'). The mock-openai parity lanes that now live in `openclaw-release-checks.yml` and `qa-live-transports-convex.yml` were still pinned to `anthropic/claude-opus-4-6` / `anthropic/claude-sonnet-4-6` for the baseline and `openai/gpt-5.4-alt` for the candidate alt model. That left the parity baseline one model-generation behind the active Opus 4.7 / GPT-5.5 defaults already used elsewhere on main (CHANGELOG.md:803, docs/providers/anthropic.md:108, openclaw-live-and-e2e-checks-reusable.yml:1894). The `approval-turn-tool-followthrough` scenario was using 20s/30s `liveTurnTimeoutMs` fallbacks that timed out on cold mock-gateway parity runs (the deleted `parity-gate.yml` env-var comments described exactly this scenario flake). Bumping all four turn fallbacks to 60s matches what the mock provider's `resolveTurnTimeoutMs` returns for fallbackMs (it returns the fallback unchanged) so cold starts have breathing room before the approval/follow-through chain has to complete. This PR does NOT touch: - The retired `.github/workflows/parity-gate.yml` (deleted on main by #74622) - Internal artifact directory names `gpt54`/`opus46` (cosmetic, out of scope for a slim follow-up) - The Discord QA scenario lane and the release-validation lane that intentionally pin `openai/gpt-5.4` (separate concerns) Refs #74290.

vincentkoc self-assigned this Apr 29, 2026

openclaw-barnacle Bot added docs Improvements or additions to documentation size: XS maintainer Maintainer-authored PR labels Apr 29, 2026

vincentkoc force-pushed the ci/parity-release-lane branch from 09c35a9 to 228a2c2 Compare April 29, 2026 21:51

vincentkoc changed the title ~~ci: make parity gate manual-only~~ ci: fold parity into QA release validation Apr 29, 2026

openclaw-barnacle Bot added extensions: qa-lab size: S and removed size: XS labels Apr 29, 2026

vincentkoc marked this pull request as ready for review May 1, 2026 11:58

vincentkoc requested a review from a team as a code owner May 1, 2026 11:58

clawsweeper Bot added the clawsweeper:automerge Maintainer opted this PR into bounded ClawSweeper-reviewed automerge label May 1, 2026

vincentkoc and others added 2 commits May 2, 2026 19:51

ci: fold parity into QA release validation

0516218

ci: fold parity into QA release validation

3482654

clawsweeper Bot force-pushed the ci/parity-release-lane branch from 228a2c2 to 3482654 Compare May 2, 2026 19:53

openclaw-barnacle Bot added scripts Repository scripts docker Docker and sandbox tooling labels May 2, 2026

clawsweeper Bot merged commit b9eb31b into main May 2, 2026
91 of 93 checks passed

clawsweeper Bot deleted the ci/parity-release-lane branch May 2, 2026 19:57

github-actions Bot mentioned this pull request May 2, 2026

📡 Upstream Digest — 2026-05-02 20:33 UTC curtismercier/openclaw-mods#749

Open

This was referenced May 3, 2026

ci: bump remaining upload-artifact actions to v7 #76354

Closed

ci: upgrade remaining v4 actions to current majors #67096

Closed

clawsweeper Bot mentioned this pull request May 3, 2026

build(deps): bump pnpm/action-setup from 4.3.0 to 6.0.3 #74984

Open

This was referenced May 8, 2026

Update QA lab parity gate for GPT-5.5 vs Opus 4.7 #74290

Closed

fix(qa-lab): bump parity baseline to Opus 4.7 / GPT-5.5 and lengthen approval-followthrough timeouts #79347

Closed

This was referenced May 10, 2026

Codex-vs-Pi runtime parity QA harness (RFC + tracking) #80171

Open

docs(qa-lab): runtime-parity gate design (Pi vs Codex harness) #80179

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

ci: fold parity into QA release validation#74622

ci: fold parity into QA release validation#74622
clawsweeper[bot] merged 2 commits intomainfrom
ci/parity-release-lane

vincentkoc commented Apr 29, 2026 •

edited

Loading

Uh oh!

vincentkoc commented May 1, 2026

Uh oh!

clawsweeper Bot commented May 1, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented May 1, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

vincentkoc commented Apr 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Testing

Uh oh!

vincentkoc commented May 1, 2026

Uh oh!

clawsweeper Bot commented May 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clawsweeper Bot commented May 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

vincentkoc commented Apr 29, 2026 •

edited

Loading

clawsweeper Bot commented May 1, 2026 •

edited

Loading

clawsweeper Bot commented May 1, 2026 •

edited

Loading