test(e2e): harden image reuse workflow validator by cv · Pull Request #7551 · NVIDIA/NemoClaw

cv · 2026-07-26T01:54:49Z

Summary

Harden the merged Hermes image-reuse workflow validator so action inputs and shell continuations cannot bypass credential, registry-write, build-cardinality, or artifact-handoff safeguards. Production workflow behavior is unchanged.

Related Issue

Part of #7451. Follow-up to #7508.

Changes

Scan action with inputs for protected secrets and reject docker/login-action outside the canonical producer authentication step.
Normalize shell continuations and recognize docker buildx build so multiline pushes and duplicate CLI builds fail closed.
Require the reviewed artifact action pins and download-before-load ordering on every Hermes artifact leg.
Add five adversarial regression tests for the reproduced bypasses.

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: this hardens an internal workflow validator and its support tests; the production workflow and documented operator contract are unchanged.
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: an independent exact-diff maintainer/security review reproduced five fail-open mutations before the patch and verified the five guarded cases after the patch.
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: no-docs-needed
Evidence: At reviewed head a6e864323, the only changes are internal E2E workflow-boundary validator hardening and adversarial support tests. The production workflow remains unchanged. Existing test/e2e/README.md already documents the Hermes producer/consumer artifact flow, exact action pins, local image loading, and disabled registry writes. The explicit affected suite passed 26/26 and npm run check:diff passed.
Agent: Codex Desktop

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; npm run check:diff also passed on exact refreshed head a6e864323.
Targeted behavior tests pass for the current change set — explicit E2E-support suite passed 26/26 on exact refreshed head. Before the main refresh, npm run test:changed -- --coverage=false also passed 26/26; after the merge-topology refresh it selected no tests, so the affected files were run explicitly.
Applicable broad gate passed — not applicable to this narrow validator/test-only delta; exact focused tests and the complete diff gate passed, and GitHub CI remains required before approval.
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

Bug Fixes
- Strengthened workflow validation for Hermes image consumers and producers.
- Blocked unauthorized Docker authentication and secret propagation in consumer jobs.
- Added validation against duplicate production builds, registry writes, and unsafe multiline commands.
- Enforced correct artifact upload/download actions, image loading, and step ordering.
- Improved detection of Docker Buildx commands and authentication methods across workflow formats.

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

coderabbitai · 2026-07-26T01:55:13Z

📝 Walkthrough

Walkthrough

The workflow boundary validator now detects action-based authentication, multiline Buildx commands, and expanded secret usage. Hermes producer and consumer checks enforce artifact ordering, canonical action pins, and authentication restrictions with updated E2E cases.

Changes

Hermes workflow boundary validation

Layer / File(s)	Summary
Detection and normalization primitives `tools/e2e/sandbox-images-workflow-boundary.mts`	Shell continuations are normalized; validation evidence includes `env`, `with`, and `run`; registry authentication detects Docker login actions and commands; Docker build extraction recognizes Buildx.
Hermes producer and consumer rules `tools/e2e/sandbox-images-workflow-boundary.mts`, `test/e2e/support/sandbox-images-workflow-boundary.test.ts`	Hermes checks reject consumer authentication, additional production builds and registry writes, enforce download-before-load ordering, require pinned artifact actions, and add targeted E2E coverage.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related issues

NVIDIA/NemoClaw issue 7451 — Covers Hermes image production and reuse changes in the same workflow boundary validator.

Possibly related PRs

NVIDIA/NemoClaw#7508 — Directly overlaps Hermes producer/consumer authentication, registry-write, and artifact action validation.

Suggested labels: integration: hermes, area: security, area: e2e, area: ci

Suggested reviewers: cjagwani, apurvvkumaria, ericksoa

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly reflects the validator hardening for Hermes image reuse workflows and the added E2E tests.
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.

✨ 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 codex/7508-validator-hardening

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

github-code-quality · 2026-07-26T01:55:33Z

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in commit a6e8643 in the codex/7508-validator... branch remains at 96%, unchanged from commit b4ef301 in the main branch.

github-actions · 2026-07-26T01:58:27Z

PR Review Advisor — Blocking findings reported

Advisor assessment: Blockers require maintainer review
Next action: Review the blockers below.
Findings: 1 blocker · 0 warnings · 0 suggestions

Model lanes

GPT-5.6 Terra (primary): Completed · high confidence · 1 blocker · 0 warnings · 0 suggestions
Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
Model comparison: normalized findings differ; normalized E2E selections match; Nemotron reported 1 fewer blocker, the same number of warnings, the same number of suggestions.

Nemotron output stays in workflow artifacts and does not change the assessment above.

E2E guidance

Advisory only. E2E / PR Gate selects and runs jobs independently.

Recommended E2E: cloud-onboard, credential-sanitization, security-posture

Blockers

`PRA-1` Blocker — Reject assigned Buildx push flags

Location: tools/e2e/sandbox-images-workflow-boundary.mts:49
Category: security
Problem: REGISTRY_WRITE recognizes `--push` only when whitespace or line end follows it. A step can use `docker buildx build --push=true ...`; that supported flag form does not match. In a consumer such as `state-dir-guard-metadata`, which has no separate Buildx-build prohibition, the validator then accepts a registry write.
Impact: A workflow change can publish an image from a consumer job, bypassing the intended no-registry-write and producer-only trust boundary.
Fix: Match `--push` with an optional Boolean assignment, including `--push=true`, and retain rejection of registry-writing Buildx commands.
Verification: Read the REGISTRY_WRITE expression and evaluate it against `docker buildx build --push=true -t registry.example.invalid/image .`; it must match.
Test coverage: Mutate a non-Hermes consumer step to run `docker buildx build --push=true ...` and assert that validateSandboxImagesWorkflow reports that the step must not write images to a registry.
Evidence: tools/e2e/sandbox-images-workflow-boundary.mts:49 matches `--push` only when `(?:\s|$)` follows the flag. tools/e2e/sandbox-images-workflow-boundary.mts:347-348 applies REGISTRY_WRITE to all workflow steps. tools/e2e/sandbox-images-workflow-boundary.mts:864-867 prohibit only `docker build`, not Buildx builds, in state-dir-guard-metadata. test/e2e/support/sandbox-images-workflow-boundary.test.ts adds a regression case for bare multiline `--push` but none for `--push=true`.

Workflow run details

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

coderabbitai

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 `@tools/e2e/sandbox-images-workflow-boundary.mts`:
- Around line 388-393: Update the Hermes consumer check around the raw step.run
inspection at line 868 to pass the command through normalizeShellContinuations
before evaluating Docker Buildx commands, so backslash-continued docker buildx
build commands trigger the consumer rebuild guard. Add a regression test
covering this continued-command form.

🪄 Autofix (Beta)

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: b3994195-5ac9-49d6-b60e-fa0466aca9b2

📥 Commits

Reviewing files that changed from the base of the PR and between b4ef301 and a6e8643.

📒 Files selected for processing (2)

test/e2e/support/sandbox-images-workflow-boundary.test.ts
tools/e2e/sandbox-images-workflow-boundary.mts

coderabbitai · 2026-07-26T01:58:28Z

 function dockerBuildLines(job: SandboxImagesWorkflowJob): string[] {
  return steps(job).flatMap((step) =>
-    (step.run ?? "")
+    normalizeShellContinuations(step.run ?? "")
      .split("\n")
      .map((line) => line.trim())
-      .filter((line) => /^docker\s+build(?:\s|$)/u.test(line)),
+      .filter((line) => /^docker\s+(?:build|buildx\s+build)(?:\s|$)/u.test(line)),


🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Normalize continued Buildx commands in the Hermes consumer check.

Line 868 still tests raw step.run, so docker \ followed by buildx build --load ... bypasses the consumer rebuild guard. Apply normalizeShellContinuations there and add the corresponding consumer regression test.

Suggested fix

- /\bdocker\s+(?:build|buildx\s+build)\b/u.test(step.run ?? ""), + /\bdocker\s+(?:build|buildx\s+build)\b/u.test( + normalizeShellContinuations(step.run ?? ""), + ),

🤖 Prompt for 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. In `@tools/e2e/sandbox-images-workflow-boundary.mts` around lines 388 - 393, Update the Hermes consumer check around the raw step.run inspection at line 868 to pass the command through normalizeShellContinuations before evaluating Docker Buildx commands, so backslash-continued docker buildx build commands trigger the consumer rebuild guard. Add a regression test covering this continued-command form.

## Summary Close the remaining Hermes image-consumer validator bypasses identified after #7551 merged. Shell continuations are normalized before the no-rebuild check, and assigned Buildx push values are evaluated case-insensitively. Literal `false` remains non-writing; true, empty, mixed-case, and dynamic or otherwise nonliteral values are rejected so the consumer cannot hide a rebuild or registry write. ## Related Issue Part of #7451. Follow-up to #7508 and #7551. ## Changes - Normalize Hermes consumer shell continuations before checking for Docker and Buildx builds. - Detect assigned, mixed-case, and dynamic Buildx registry-push values in the consumer guard. - Preserve literal `--push=false` as non-writing. - Add adversarial regressions for multiline rebuilds and assigned push values. ## Type of Change - [x] 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 - [x] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [ ] Tests not applicable — justification: - [ ] Docs updated for user-facing behavior changes - [x] Docs not applicable — justification: the production workflow and documented no-rebuild contract are unchanged; this makes the internal validator enforce that existing contract for continued commands. - [x] Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging) - [x] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: CodeRabbit reproduced the bypass on #7551; the exact mutation is now an adversarial test and passes only with normalization at the consumer guard. - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Documentation Writer Review - [x] Documentation writer subagent reviewed the completed changes - Result: `no-docs-needed` - Evidence: At PR SHA `2cef897b4fcba8033d115d94f2dd4c2ae12d86ed`, the change only strengthens the repository-internal Hermes image-consumer validator for multiline rebuilds and assigned, mixed-case, or dynamic Buildx push values. Literal `--push=false` remains non-writing. `test/e2e/README.md` already documents the no-rebuild/no-registry-write contract. The focused E2E-support suite passed 29/29, the PR workflow-contract suite passed 22/22, and `npm run build:cli` plus `npm run check:diff` passed. - Agent: Codex Desktop   ## DGX Station Hardware Evidence - [ ] Tested on DGX Station - Tested commit: - Station profile/scenario: - Result: - Supporting evidence: ## Verification - [x] PR description includes a `Signed-off-by:` line and every commit appears as `Verified` in GitHub - [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed; `npm run build:cli` and `npm run check:diff` also passed on exact head `2cef897b4fcba8033d115d94f2dd4c2ae12d86ed`. - [x] Targeted behavior tests pass for the current change set — E2E-support passed 29/29 and the PR workflow-contract suite passed 22/22. - [x] Applicable broad gate passed — not applicable to this validator/test-only delta; the exact affected suites, CLI build, and complete diff gate passed, and GitHub CI remains required before approval. - [x] Quality Gates section completed with required justifications or waivers - [x] 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 * **Bug Fixes** * Improved sandbox image workflow validation to more precisely detect `docker buildx build ... --push` commands, including shell line continuations and `--push` casing/formatting. * Strengthened Hermes prebuilt-image reuse checks by normalizing command formatting before validating consumer steps. * **Tests** * Added new end-to-end negative cases covering consumer attempts to rebuild the prebuilt Hermes production image. * Added coverage to ensure consumers attempting registry writes via `--push` are rejected, while explicitly using `--push=false` is allowed.  --------- Signed-off-by: Carlos Villela <cvillela@nvidia.com> Signed-off-by: Apurv Kumaria <akumaria@nvidia.com> Signed-off-by: Charan Jagwani <cjagwani@nvidia.com> Co-authored-by: Apurv Kumaria <akumaria@nvidia.com> Co-authored-by: Charan Jagwani <cjagwani@nvidia.com>

## Summary Add the canonical `docs/changelog/2026-07-25.mdx` release entry with the exact `## v0.0.96` heading. The entry reconciles all 90 first-parent commits since v0.0.95 with all 92 merged PRs in the live `v0.0.96` label ledger and groups the user-visible changes by operator journey. ## Changes - Add the parser-safe dated MDX changelog entry for v0.0.96 with root-absolute links to the focused user guides. - Source summary: - [#7194](#7194) -> `docs/changelog/2026-07-25.mdx`: Document persistent baseline network policy exclusions and their inspection, rebuild, and snapshot behavior. - [#7188](#7188), [#7427](#7427), and [#7546](#7546) -> `docs/changelog/2026-07-25.mdx`: Document DNS-backed HTTPS inference routing, keyless loopback endpoints, and provider-marker isolation. - [#7238](#7238) -> `docs/changelog/2026-07-25.mdx`: Document blueprint sandbox and provider identifier validation before state writes or OpenShell calls, with bounded terminal-safe rejection previews. - [#7319](#7319), [#7274](#7274), [#7528](#7528), [#7353](#7353), and [#7560](#7560) -> `docs/changelog/2026-07-25.mdx`: Document the managed default gateway service, onboarding readiness, and container-runtime identity safeguards. - [#7349](#7349), [#7498](#7498), [#7406](#7406), [#7196](#7196), [#7559](#7559), [#7421](#7421), [#7510](#7510), [#7295](#7295), and [#7565](#7565) -> `docs/changelog/2026-07-25.mdx`: Document gateway-scoped status, lifecycle diagnostics, managed MCP recovery, delete-edge safeguards, and fail-closed CLI prompt and command output. - [#7591](#7591) -> `docs/changelog/2026-07-25.mdx`: Document opt-in authenticated MCP tool-name discovery, its bounded and names-only contract, probe interaction, and rebuild requirement. - [#7305](#7305), [#7480](#7480), [#7471](#7471), [#7365](#7365), and [#7541](#7541) -> `docs/changelog/2026-07-25.mdx`: Document installer version checks, version-tag reporting, license guidance, WSL Ollama selection, and DGX Station vLLM detection. - [#7482](#7482), [#7466](#7466), [#7208](#7208), [#7434](#7434), and [#7586](#7586) -> `docs/changelog/2026-07-25.mdx`: Document Ollama resource details, reasoning precedence, Hermes onboarding behavior, and preserved managed Hermes BuildKit failures. - [#6830](#6830), [#7492](#7492), [#7563](#7563), and [#7582](#7582) -> `docs/changelog/2026-07-25.mdx`: Document the authoritative OpenClaw production lock, fixed managed-image dependencies, immutable Hermes base adoption, and Hermes image-size reduction. - [#7505](#7505), [#7530](#7530), [#7547](#7547), [#7508](#7508), [#7548](#7548), [#7549](#7549), [#7537](#7537), [#7534](#7534), [#7515](#7515), [#7511](#7511), [#7551](#7551), [#7562](#7562), [#7575](#7575), [#7496](#7496), [#7594](#7594), [#7595](#7595), and [#7599](#7599) -> `docs/changelog/2026-07-25.mdx`: Summarize release validation, transient and bounded dispatch reconciliation, exact pre-tag qualification, identity revalidation, npm-audit retry, sharding, image reuse, timeout, telemetry, and workflow-hardening changes. - Reconciled without separate changelog prose: - [#7539](#7539), [#7526](#7526), [#7507](#7507), [#7506](#7506), [#7519](#7519), [#7516](#7516), [#7396](#7396), [#7254](#7254), [#7583](#7583), [#7596](#7596), and [#7598](#7598): Test-harness or fixture-only changes. - [#7403](#7403), [#7161](#7161), [#6877](#6877), [#7531](#7531), [#7525](#7525), [#7522](#7522), [#7536](#7536), [#7552](#7552), [#7566](#7566), [#7553](#7553), [#7561](#7561), [#7577](#7577), [#7569](#7569), [#7585](#7585), [#7584](#7584), [#7592](#7592), [#7580](#7580), [#7571](#7571), [#7517](#7517), [#7589](#7589), [#7402](#7402), [#7558](#7558), [#7544](#7544), and [#7601](#7601): Dependency, internal recovery, validation, contributor-workflow, E2E optimization, telemetry, or CI trust changes with no separate user-facing release claim. - [#7556](#7556), [#7573](#7573), [#7576](#7576), and [#7578](#7578): Experimental repository-maintainer conflict automation with no canonical user documentation surface. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [x] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates - [ ] Tests added or updated for changed behavior - [x] Existing tests cover changed behavior — justification: `test/changelog-docs.test.ts` validates dated changelog structure, version headings, and published links. - [ ] Tests not applicable — justification: - [x] 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: - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Documentation Writer Review - [x] Documentation writer subagent reviewed the completed changes - Result: `docs-updated` - Evidence: Reviewed `docs/changelog/2026-07-25.mdx` at exact head `0f5dedb47` against 90 first-parent release commits and 92 merged PRs labeled `v0.0.96`. Verified parser-safe MDX SPDX, the exact version heading, literal CLI names, writing style, skip terms, all 20 root-absolute published links, and the accepted #7591 opt-in authenticated discovery bounds. #7544, #7599, and #7601 remain internal or CI-only release-ledger entries. Changelog tests passed 6/6, the docs build passed with 0 errors and two pre-existing Fern warnings, and `npm run check:diff` plus the final diff check passed. - Agent: Codex Desktop documentation-writer subagent   ## DGX Station Hardware Evidence - [ ] Tested on DGX Station - Tested commit: - Station profile/scenario: - Result: - Supporting evidence: ## Verification - [x] PR description includes a `Signed-off-by:` line and every commit appears as `Verified` in GitHub - [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or `npm run check:diff` passed when hooks were skipped or unavailable - [x] Targeted behavior tests pass for the current change set, or tests are marked not applicable above — `npx vitest run test/changelog-docs.test.ts`: 6/6 passed. - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — command/result: Not applicable to this prose-only changelog entry. - [x] Quality Gates section completed with required justifications or waivers - [x] No secrets, API keys, or credentials committed - [ ] `npm run docs` builds without warnings (doc changes only) — the build passed with 0 errors and 2 existing Fern warnings; the published-route check passed. - [x] Doc pages follow the [style guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md) (doc changes only) - [ ] New doc pages include SPDX header and frontmatter (new pages only) — native changelog files use the required parser-safe MDX SPDX comment and no frontmatter. --- Signed-off-by: Carlos Villela <cvillela@nvidia.com>  ## Summary by CodeRabbit * **New Features** * Persistent network policy exclusions with consistent restore/exclusion reporting across rebuilds/snapshots. * Opt-in MCP tool discovery via `mcp status --tools` with bounded, redacted authenticated traffic. * Improved HTTPS inference switching for custom endpoints and refreshed onboarding/model menu details. * Refined OpenShell gateway defaults for port `8080`, including more reliable readiness checks. * **Bug Fixes** * Prevent incorrect provider/model restoration after compatible-provider update failures. * Preserve managed MCP state after exec loss and tighten gateway/doctor status scoping. * **Tests** * Stronger, fail-closed release validation with hardened evidence/artifact handoff and bounded timeouts/retries.  --------- Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com> Co-authored-by: Prekshi Vyas <prekshiv@nvidia.com>

cv added 2 commits July 25, 2026 18:43

test(e2e): harden image reuse workflow validator

b531aed

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

merge(main): refresh validator hardening

a6e8643

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

cv added the v0.0.96 label Jul 26, 2026

coderabbitai Bot reviewed Jul 26, 2026

View reviewed changes

cv merged commit 4fdbb79 into main Jul 26, 2026
73 of 76 checks passed

cv deleted the codex/7508-validator-hardening branch July 26, 2026 02:00

cv mentioned this pull request Jul 26, 2026

test(e2e): reject continued Hermes consumer builds #7553

Merged

23 tasks

cjagwani mentioned this pull request Jul 26, 2026

ci: split E2E feedback-loop work into focused PRs #7451

Closed

9 tasks

cv mentioned this pull request Jul 26, 2026

docs: add v0.0.96 release entry #7564

Merged

23 tasks

wscurran added area: ci CI workflows, checks, release automation, or GitHub Actions area: e2e End-to-end tests, nightly failures, or validation infrastructure integration: hermes Hermes integration behavior labels Jul 29, 2026

Navigation Menu

Uh oh!

test(e2e): harden image reuse workflow validator - #7551

test(e2e): harden image reuse workflow validator#7551
cv merged 2 commits into
mainfrom
codex/7508-validator-hardening

cv commented Jul 26, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Jul 26, 2026 •

edited

Loading

Walkthrough

Changes

Uh oh!

github-code-quality Bot commented Jul 26, 2026

Uh oh!

github-actions Bot commented Jul 26, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot Jul 26, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

cv commented Jul 26, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Related Issue

Changes

Type of Change

Quality Gates

Documentation Writer Review

DGX Station Hardware Evidence

Verification

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Jul 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

github-code-quality Bot commented Jul 26, 2026

Code Coverage Overview

TypeScript / code-coverage/plugin

Uh oh!

github-actions Bot commented Jul 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review Advisor — Blocking findings reported

Model lanes

E2E guidance

Blockers

PRA-1 Blocker — Reject assigned Buildx push flags

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Jul 26, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

cv commented Jul 26, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jul 26, 2026 •

edited

Loading

github-actions Bot commented Jul 26, 2026 •

edited

Loading

`PRA-1` Blocker — Reject assigned Buildx push flags