fix(ci): skip implicit Portable npm audit - #11068
Conversation
|
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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe workflow selects npm audit behavior by trigger. Automated runs disable auditing, while manual runs enable it. Contract tests validate both paths and their ordering. ChangesDependency audit routing
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to Automated Portable runs now skip npm audit while manual dispatches retain audit visibility, with contract coverage for both paths. No current merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Candidate evidence disposition (
|
rsliter
left a comment
There was a problem hiding this comment.
Approved at ae0d5281adc51043e1200819249fdc062f402f09.
The accepted #11028 scope permits removing redundant advisory requests while the reviewed production-graph audit remains the enforcing gate. The prior install-time audit was best-effort visibility: base evidence shows it reported vulnerabilities and continued, so suppressing it on automated Portable runs does not remove a fail-closed control. Manual dispatch retains that visibility. The trigger split and ordering are covered by the workflow contract test.
Required checks pass. The supplemental rootless job failed at the unchanged Hermes dashboard readiness phase after the image build, matching the base run; cleanup passed. I re-evaluated the PR Review Advisor objections and CodeRabbit feedback. They do not identify a PR-attributable blocker.
|
PR Review Advisor finished for commit |
Outcome
Automated Portable rootless E2E runs no longer send an implicit npm advisory request while installing root dependencies. Manual workflow dispatches retain an explicit install-time audit; reviewed npm-audit gates and the accepted best-effort behavior for concurrent exact-input cache misses are unchanged.
Reason
Portable run 33879304029 showed both the rootless job and portable-launch job implicitly auditing 506 packages from the same checkout lock. Neither install-time result enforces NemoClaw policy or emits reviewed evidence. Main CI for the same revision separately evaluated the candidate through the reviewed production-graph audit.
These requests do not have identical audit inputs. Issue #11028 accepts concurrent exact-input cache misses and rejects global serialization solely to guarantee one request. This change preserves that tradeoff and removes a different observed source of registry work.
Related issues
Refs #11028
Changes
--no-audit --no-fund, whileworkflow_dispatchuses explicit--audit --no-fund.The shared pinned prepare-E2E action remains unchanged because changing it would affect many consumers and require a separate provenance repin.
Verification
npm run validate:pr— passed pre-commit, commit-message, and pre-push checks. Pinned hook source trees and release artifacts were verified locally after direct GitHub Git transport returned HTTP 503.npx vitest run --project e2e-support test/e2e/support/portable-profile-rootless-runtime-workflow.test.ts— 4 tests passed.npm run source-shape:check— passed.npm run checks:repository— passed.npm run test:projects:check— passed; 2,588 files mapped across 7 projects.npm run test:changed— passed; the catalogue compiled and 45 growth tests passed. The focused test separately verified the changed workflow contract.git diff --check— passed.Review notes
Issue #11028 contains the accepted scope and trust decision. This workflow change does not alter cache-writer trust, freshness checks, policy evaluation, fail-closed behavior, graph receipts, Docker audit fallback, or signature verification. Manual install-time audit remains best-effort visibility rather than a fail-closed policy decision; the reviewed production-graph audit remains authoritative for pull requests and main.
Concurrent cache misses remain best-effort by the accepted decision. The first Advisor cycle identified the manual-dispatch gap; the repair preserves its audit and passed three independent pre-publication reviews with no remaining findings.
Signed-off-by: cjagwani cjagwani@nvidia.com
Summary by CodeRabbit
Chores
Tests