fix(ci): make owner-approved Testbox landing reliable#104726
Merged
Conversation
Contributor
Author
|
Land-ready maintainer proof:
This fixes the owner landing path itself: an explicit owner/maintainer instruction to land reviewed PRs now counts as Testbox authorization, and nested gateway CPU checks no longer inherit the outer dependency-install policy. |
Contributor
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 12, 2026
* fix(ci): isolate nested pnpm verification * test(google): verify OAuth abort signal forwarding * docs: treat owner land requests as Testbox approval
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
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.
What Problem This Solves
Owner-approved contributor landing through
OPENCLAW_PR_GATES_REMOTE=testboxcurrently fails unrelated full-suite tests. The outer gate intentionally setsPNPM_CONFIG_VERIFY_DEPS_BEFORE_RUN=install, but nested gateway CPU scenarios inherit that value even though their build contract requires dependency re-verification to stay disabled. The Google local OAuth test also remained on the old two-argument token-exchange expectation after abort-signal forwarding was added.Why This Change Was Made
PNPM_CONFIG_VERIFY_DEPS_BEFORE_RUN=falseafter the outer Testbox has hydrated dependencies.User Impact
No product runtime behavior changes. Maintainers can land reviewed fork PRs through the native owner-approved Testbox path without a redundant authorization prompt or environment-dependent tooling failures.
Evidence
tbx_01kx9jqxzxc314etvn400cf9pj/ Actions run 29169574508: 15 gateway CPU scenario tests and the Google OAuth local-login test passed with outerPNPM_CONFIG_VERIFY_DEPS_BEFORE_RUN=install.pnpm exec oxfmt --checkon the three code/test files.git diff --check.