fix(ci): select trusted release harness for Docker lanes#103504
Merged
Conversation
openclaw-barnacle
Bot
added
scripts
vincentkoc
marked this pull request as ready for review
July 10, 2026 07:03
Member
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #103451
What Problem This Solves
Fixes an issue where targeted Docker release lanes loaded from the trusted
.release-harnesscheckout would still execute the release candidate's stale harness scripts. This produced a false-negative Codex npm plugin gate after the provider preflight and all three live turns had passed.Why This Change Was Made
Correct the path-component detector so a scenario catalog imported from
.release-harness/scripts/libdefaultsOPENCLAW_DOCKER_E2E_TRUSTED_HARNESS_DIRto.release-harness. Keep ordinary source-checkout planning on the existing.default.The regression test imports the real scenario catalog from a temporary nested
.release-harnesspath and inspects the exact generatedlive-codex-npm-plugincommand.User Impact
Release operators can apply harness-only fixes on trusted
mainwithout changing a frozen release candidate. Targeted Docker release lanes now execute those trusted scripts instead of silently falling back to candidate-side copies.Evidence
86302246029: Codex preflight and 3/3 live turns passed, then the candidate's stale assertion ran.5b95b65671f9717c5225d341468c92c6dd0c5e29.tbx_01kx5d3yg1r003re038s9fwh6v, run https://github.com/openclaw/openclaw/actions/runs/29075281155: focuseddocker-e2e-plantests passed 33/33.pnpm check:changedpassed and reported no new test temp-directory migration warnings..release-harnessmodule defaults to.release-harnessand invokesscripts/e2e/codex-npm-plugin-live-docker.sh.git diff --checkpassed.This replaces #103494, which GitHub would not reopen after its branch was force-pushed to the rebased exact head.