<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 -->

Update Dependencies

Treat an upgrade as a migration, not a version edit. Explain the changed upstream contracts, their NemoClaw consumers, the required migrations, and the evidence for each conclusion.

Load this workflow from nemoclaw-contributor-implement-issue for a dependency upgrade. nemoclaw-contributor-implement-issue still owns issue scope and handoff; this workflow owns the upgrade procedure.

Mutation boundary

Change only the NVIDIA/NemoClaw checkout in scope. Treat upstream repositories, registries, workflows, issue trackers, and PRs as read-only. Report an upstream defect and its downstream effect. Require a separate user request for upstream changes.

Plan the upgrade

Add these outcomes to the working plan:

• Resolve the current and target source and artifact identities.
• Audit every adjacent release range.
• Map changed upstream contracts to current downstream consumers.
• Record security, lifecycle, state, packaging, and compatibility concerns.
• Implement required migrations before changing the final selector.
• Add concern-specific tests and runtime evidence.
• Verify the artifacts and selectors used by the PR head.

An unresolved high-impact concern blocks the upgrade.

Discover current contracts

Follow Discover the Current Implementation.

Search from the current dependency identity and each changed upstream identifier. Trace consumers through source, tests, configuration, generated inputs, packaging, workflows, and documentation. Do not maintain a path or selector inventory in this skill.

Audit upstream changes

For each adjacent release range: