Repository navigation
feat(ci): promote Deep Agents Code managed image pointers - #12371
Conversation
Extends the shipped-agent pointer set from (openclaw hermes) to include langchain-deepagents-code at both managed-images.yaml sites, so the promote lane records and moves :<revision> and :<release> consumer pointers for the Deep Agents Code image it already builds, validates, attests, and stages in the six-candidate cohort barrier (#11341). Stock Deep Agents Code onboarding already consumes this image buildless by exact digest, and SHIPPED_MANAGED_IMAGE_AGENTS already names the agent shipped; only the consumer pointers were missing, so downstream custom images (nemo-deepagents onboard --from) had nothing to FROM by name. This aligns the workflow's pointer set with the source contract's shipped-agent list. The publication tests now prove the Deep Agents Code pointer moves only after all cohort aliases stage and that a barrier failure moves no pointer for any agent. The quickstart documents starting custom images FROM the published image. Signed-off-by: Zac Wang <zacw@nvidia.com> (cherry picked from commit 532622e) Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: NVIDIA/NemoClaw/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 10 remain after this review. 📝 WalkthroughWalkthroughThe managed-image workflow adds Deep Agents Code to consumer alias staging and root-pointer promotion. Tests cover pointer ordering and release-alias contents. The quickstart describes using the published image as a digest-pinned base for a custom Dockerfile. ChangesManaged image publication
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Feature · Severity of issue fixed: Medium Suggested reviewers: Merge Risk: ⚪ Minimal · up to No actionable issue is established for the Deep Agents Code image-pointer change; normal CI validation remains appropriate before merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
🌿 Preview your docs: https://nvidia-preview-pr-12371.docs.buildwithfern.com/nemoclaw |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall line coverage in commit 61ca6bc in the TypeScript / code-coverage/cliThe overall line coverage in commit 61ca6bc in the Show a line coverage summary of the most impacted files.
Updated |
|
Review disposition for 7ece0a3. All nine Advisor artifacts were collected and their digests and commit/run provenance verified.
The other six specialists are clear. CodeRabbit reviewed all four original changed files without actionable findings; its docstring warning is advisory. The raw Advisor result remains unchanged. The test-only follow-up will receive fresh CI and automated review before merge. |
Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
PR Review Advisor finished for commit Request review only when Require no Advisor blockers is green. |
|
Final review disposition for 61ca6bc. All nine Advisor reports were collected and their artifact digests, commit identities, and run provenance verified. Seven reports are clear, including verification, security, and architecture. CodeRabbit reviewed the follow-up and reports no actionable findings.
The earlier release-tag evidence gap is fixed. Forty focused tests pass, including the new release alias ordering and byte-identity case. Deliberately omitting only the Deep Agents release alias leaves the prior revision test passing and makes the new test fail; the production workflow was restored unchanged. The raw Advisor result remains failure and is not rewritten. No candidate-owned code blocker remains. Public release-tag resolution and downstream use remain the explicitly recorded normal release-process verification; no pre-merge live publication or full E2E matrix is claimed. |
|
Maintainer approval for merge at 61ca6bc, under the explicit instruction to deliver this contribution after green CI. Validation: 40 focused publication tests, documentation validation, required code CI, managed-image qualification on Docker and rootless Podman, and the repository's self-hosted PR qualification passed. Both commits are GitHub Verified. Zac Wang's contribution and authorship are retained; the follow-up adds only the release-tag regression and fixture support. Code CI: https://github.com/NVIDIA/NemoClaw/actions/runs/36369830231 GitHub does not allow this account to submit an approval review on a PR it opened. The previously authorized admin merge records the maintainer decision for this owner replay after technical validation. This is not independent human approval. The Advisor's raw result is retained with the false-positive and unchanged-text dispositions above. |
Outcome
Publish Deep Agents Code managed-image release and revision tags alongside OpenClaw and Hermes. Custom Dockerfiles can resolve a release and pin its complete image digest. Stock onboarding retains its existing digest resolution.
Reason
The workflow already builds, qualifies, attests, and stages Deep Agents Code on AMD64 and ARM64, but omits it from consumer tag promotion.
This replays Zac Wang's #11342 on an NVIDIA-owned branch because the required reviewed OpenShell SDK is unavailable to fork CI. Zac remains the author of the replay commit; a separate test-only commit adds release-alias regression coverage.
Related issues
Resolves #11341. Supersedes #11342 after this replacement merges.
Changes
Verification
npx vitest run test/inference/managed/managed-image-publication-promotion.test.ts test/inference/managed/managed-image-publication-workflow.test.ts.npm run docspassed with zero Fern errors and two warnings. Normal commit and publication checks passed.61ca6bc5ae8d02b36cc34209574a857ef250dac1; base:3c668364eeb9b94dcd2e0a553382aa0e16e3745e. Both published commits are GitHub Verified.Review notes
Maintainer decision: Accept. The existing managed-image maintainers own the Linux AMD64/ARM64 publication lifecycle; Aaron Erickson is accountable for this delivery. The decision records scope, compatibility, security controls, and validation.
CodeRabbit reviewed the original change and the test follow-up without actionable findings. All nine current-commit Advisor reports were collected and their artifact digests and provenance verified. Seven reports are clear. The remaining authority finding contradicts fresh GitHub MEMBER/admin evidence, and the workflow-overview suggestion concerns unchanged text already present while main published Hermes consumer pointers. The stock OpenClaw-led catalog discovery owner remains unchanged. Complete review disposition. The raw Advisor failure is preserved; no candidate-owned code blocker remains.
Self-review covered the workflow, both publication test files, their fixture helper, and the quickstart. Every cohort is validated before staging; every shipped-agent reference is verified before consumer aliases move; alias readback must match the immutable cohort bytes.
Signed-off-by: Aaron Erickson aerickson@nvidia.com
Summary by CodeRabbit