Skip to content

ci(workflows): remove obsolete base compatibility paths - #8636

Merged
cv merged 7 commits into
mainfrom
ci/remove-obsolete-workflow-bootstraps
Aug 9, 2026
Merged

ci(workflows): remove obsolete base compatibility paths#8636
cv merged 7 commits into
mainfrom
ci/remove-obsolete-workflow-bootstraps

Conversation

@cv

@cv cv commented Aug 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

Pull request CI previously carried compatibility branches for base revisions that lacked current trusted helpers. The workflows now execute the helpers from the PR base SHA and fail when that trusted interface is absent.

Changes

  • Remove installer integration, WeChat audit, reviewed npm audit, Pi tool, and E2E-support fallback paths from .github/workflows/pr.yaml.
  • Remove the expired installer hash bootstrap and execute only the base-trusted checker for pull requests.
  • Remove capability probes that skipped ShellCheck reporting and growth guardrails on older base revisions.
  • Update growth-guardrail trust hashes and remove tests for the deleted installer bootstrap.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Quality Gates

  • Tests added or updated for changed behavior
  • Existing tests cover changed behavior — justification:
  • Tests not applicable — justification:
  • Docs updated for user-facing behavior changes
  • Docs not applicable — justification:
  • Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
  • Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: Self-review against the repository Security Rubric confirmed that executable PR checks still come from the PR base. Growth-guardrail mutation tests still reject checkout of the latest PR commit and untrusted action execution.
  • Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Documentation Writer Review

  • Documentation writer subagent reviewed the completed changes
  • Result: docs-updated
  • Evidence: Updated agents/openclaw/dependency-review.md and docs/security/openclaw-2026.6.10-dependency-review.md. The writer verified exact PR base SHA claims and installer trust-boundary coverage. npm run docs passed with 0 errors and 2 existing hidden warnings.
  • Agent: Pi CLI

DGX Station Hardware Evidence

  • Tested on DGX Station
  • Tested commit:
  • Station profile/scenario:
  • Result:
  • Supporting evidence:

Verification

  • PR description includes a Signed-off-by: line and every commit appears as Verified in GitHub
  • Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run validate:pr passed after refreshing origin/main when hooks were skipped or unavailable
  • Targeted behavior tests pass for the current change set, or tests are marked not applicable above — npx vitest run --project integration test/pr-workflow-contract.test.ts — 1 file and 5 tests passed; npm run source-shape:check and npm run test-conditionals:scan passed.
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result:
  • Quality Gates section completed with required justifications or waivers
  • No secrets, API keys, or credentials committed
  • npm run docs builds without warnings (doc changes only)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Carlos Villela cvillela@nvidia.com

Summary by CodeRabbit

  • Workflow Improvements

    • Streamlined automated security, auditing, installation, and code-quality checks.
    • Standardized validation around trusted base-commit actions.
    • Ensured required tools and checks run consistently.
    • Removed legacy fallback and bootstrap validation paths.
    • Improved fail-closed behavior when required auditing tools are unavailable.
  • Tests

    • Updated workflow policy tests for revised approved steps and trusted execution checks.
  • Documentation

    • Clarified trusted execution and security-audit requirements for pull requests.

@cv cv self-assigned this Aug 9, 2026
@coderabbitai

coderabbitai Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Changes

The CI workflows now invoke trusted base-commit actions directly. They remove tool detection, bootstrap checkout and validation, fallback execution, and related contract paths. Shell scanning and growth guardrail checks run unconditionally.

Trusted CI workflows

Layer / File(s) Summary
Unconditional validation and scanning
.github/workflows/code-scanning.yaml, .github/workflows/codebase-growth-guardrails.yaml, tools/growth-guardrails/workflow-boundary.mts, test/growth-guardrails-workflow-boundary.test.ts
Shell scanning and growth guardrail checks no longer depend on tool-presence detection. Approved workflow hashes and the boundary test expectation were updated.
Direct installer-hash verification
.github/workflows/installer-hash-check.yaml, scripts/check-installer-hash.sh, test/pr-workflow-contract.test.ts, ci/source-shape-test-budget.json
The installer-hash workflow directly invokes the base-trusted checker. Trust-boundary documentation, contract tests, and source-shape exceptions enforce base-SHA execution.
Trusted pull-request action integrations
.github/workflows/pr.yaml, agents/openclaw/dependency-review.md, docs/security/openclaw-2026.6.10-dependency-review.md, test/reviewed-npm-audit-workflow.test.ts
Installer integration, WeChat auditing, npm auditing, and eight-shard CLI coverage directly invoke trusted base-commit actions. Bootstrap exceptions, fallback paths, and related test constants were removed.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant PullRequest
  participant PRCheckout
  participant BaseTrustedCheckout
  PullRequest->>PRCheckout: provide workflow and installer data
  PullRequest->>BaseTrustedCheckout: invoke trusted base-commit actions
  BaseTrustedCheckout->>PRCheckout: run checks and return results
Loading

Possibly related PRs

Suggested labels: bug-fix, v0.0.106

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: removing obsolete CI compatibility paths from the workflows.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/remove-obsolete-workflow-bootstraps

Comment @coderabbitai help to get the list of available commands.

@github-code-quality

github-code-quality Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in commit 80c9665 in the ci/remove-obsolete-w... branch remains at 96%, unchanged from commit 290eb94 in the main branch.


Updated August 09, 2026 02:43 UTC

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — No blocking findings reported

Advisor assessment: No blocking advisor findings reported
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions

Model lanes

  • GPT-5.6 Terra (primary): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
  • Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
  • Model comparison: normalized findings match; normalized terminology decisions differ; normalized E2E selections differ; severity counts match.
2 additional E2E selections from the second opinion

Advisory only. The primary lane did not select these E2E jobs or targets.

  • bootstrap-install-smoke: The completed second-opinion lane identified E2E coverage that the primary lane omitted.
  • network-policy: The completed second-opinion lane identified E2E coverage that the primary lane omitted.

Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests.

2 semantic terminology decisions

Terminology decisions are advisory. They affect the assessment only when a separate finding identifies concrete semantic impact.

  • established — base-trusted at test/pr-workflow-contract.test.ts:286: Retain `base-trusted` for code checked out from the PR base SHA.
  • established — latest PR commit at .github/workflows/installer-hash-check.yaml:44: Retain `latest PR commit` when distinguishing PR data from base-SHA executable code.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite against this exact revision.

Recommended E2E: cloud-inference, cloud-onboard, managed-image-multiarch-startup, security-posture

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@test/pr-workflow-contract.test.ts`:
- Around line 313-320: Update the allowed-executor validation around
allowedExecutors and installerHashTrustViolations so the local
ci-installer-hash-check action is permitted only when its step condition
excludes pull requests; reject PR-only conditions such as github.event_name ==
'pull_request'. Add a fixture containing a PR-only local executor and assert
that installerHashTrustViolations reports it.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 18320702-800b-4a63-aa86-4cce868cd345

📥 Commits

Reviewing files that changed from the base of the PR and between 0b15453 and 51b5250.

📒 Files selected for processing (6)
  • agents/openclaw/dependency-review.md
  • ci/source-shape-test-budget.json
  • docs/security/openclaw-2026.6.10-dependency-review.md
  • scripts/check-installer-hash.sh
  • test/pr-workflow-contract.test.ts
  • test/reviewed-npm-audit-workflow.test.ts
💤 Files with no reviewable changes (1)
  • test/reviewed-npm-audit-workflow.test.ts

Comment thread test/pr-workflow-contract.test.ts Outdated
@cv
cv merged commit 038e823 into main Aug 9, 2026
87 of 90 checks passed
@cv
cv deleted the ci/remove-obsolete-workflow-bootstraps branch August 9, 2026 02:51
@github-actions github-actions Bot added the v0.0.106 Release target label Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v0.0.106 Release target

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant