chore(beep boop 🤖): Bump uv.lock (main) (2026-03-13)

[svcnvidia-nemo-ci]

🚀 PR to bump uv.lock in main.

🤖 This PR will be merged automatically once CI passes.

Summary by CodeRabbit

• Chores
  • Updated internal dependencies to latest versions.

[svcnvidia-nemo-ci]

/ok to test 71446d2

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates the Megatron-LM submodule pointer to a new commit SHA across .main.commit and 3rdparty/Megatron-LM. No functional code changes, only dependency reference updates.

Changes

Cohort / File(s)	Summary
Megatron-LM Submodule Update .main.commit, 3rdparty/Megatron-LM	Updates the Megatron-LM submodule commit reference from 251a754... to 7ca9dc5...

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(beep boop 🤖): Bump uv.lock (main) (2026-02-06) #2256: Updates the Megatron-LM submodule pointer to a different commit
• chore(beep boop 🤖): Bump uv.lock (main) (2026-02-17) #2399: Updates the 3rdparty/Megatron-LM submodule pointer reference
• chore(beep boop 🤖): Bump uv.lock (r0.3.0) (2026-02-12) #2348: Updates the Megatron-LM submodule pointer to a new commit SHA

Suggested reviewers

• yaoyu-33
• maanug-nv

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions bumping uv.lock, but the actual changes show updates to .main.commit and a Megatron-LM submodule pointer, not a uv.lock file.	Update the title to accurately reflect the actual changes: submodule version updates rather than uv.lock bumps, or verify the correct files were modified.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Test Results For Major Changes	✅ Passed	PR contains only minor routine dependency updates (submodule pointer changes) as part of automated CI workflow. No new features, breaking changes, or significant refactoring introduced.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bump-ci-container-2026-03-13-main-main

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

Tip

CodeRabbit can use TruffleHog to scan for secrets in your code with verification capabilities.

Add a TruffleHog config file (e.g. trufflehog-config.yml, trufflehog.yml) to your project to customize detectors and scanning behavior. The tool runs only when a config file is present.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@3rdparty/Megatron-LM`:
- Line 1: PR metadata is inconsistent: the change updates the
3rdparty/Megatron-LM git submodule pointer but the title/description mention
bumping uv.lock; update the PR title and description to accurately state "Update
3rdparty/Megatron-LM submodule pointer" (or similar), amend the commit message
that touched 3rdparty/Megatron-LM to reflect the submodule update, and if the
intent was actually to update uv.lock instead, revert this submodule change and
apply the uv.lock modification; ensure references to "3rdparty/Megatron-LM" and
"uv.lock" in the PR text match the actual files changed.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3997bdee-a2f5-4d59-8eb8-2013a223d4db

📥 Commits

Reviewing files that changed from the base of the PR and between 1508d04 and 71446d2.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• .main.commit
• 3rdparty/Megatron-LM

[coderabbitai]

⚠️ Potential issue | 🟠 Major

PR title and description are inconsistent with actual changes.

The PR title states "Bump uv.lock (main)" and the description mentions updating the uv.lock file, but the actual change is updating the Megatron-LM git submodule pointer. There is no uv.lock file modification in this PR. This creates confusion about the purpose and scope of the changes.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@3rdparty/Megatron-LM` at line 1, PR metadata is inconsistent: the change
updates the 3rdparty/Megatron-LM git submodule pointer but the title/description
mention bumping uv.lock; update the PR title and description to accurately state
"Update 3rdparty/Megatron-LM submodule pointer" (or similar), amend the commit
message that touched 3rdparty/Megatron-LM to reflect the submodule update, and
if the intent was actually to update uv.lock instead, revert this submodule
change and apply the uv.lock modification; ensure references to
"3rdparty/Megatron-LM" and "uv.lock" in the PR text match the actual files
changed.