chore(beep boop 🤖): Bump uv.lock (r0.4.0, mcore-core_r0.17.0) (2026-04-17)

[svcnvidia-nemo-ci]

🚀 PR to bump uv.lock in r0.4.0.

🤖 This PR will be merged automatically once CI passes.

Summary by CodeRabbit

• Chores
  • Updated internal dependency references to latest compatible versions.

[svcnvidia-nemo-ci]

/ok to test 6de03f1

[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

The pull request updates the Megatron-LM submodule reference by changing the tracked commit hash in both .main.commit and the 3rdparty/Megatron-LM submodule pointer from d7288711ba278d160d2a5a22c099915c9fe1395c to d6b1813f2bfb867661b154574d76b3c0d395f426.

Changes

Cohort / File(s)	Summary
Megatron-LM Submodule Bump .main.commit, 3rdparty/Megatron-LM	Updated submodule commit reference to new hash d6b1813f2bfb867661b154574d76b3c0d395f426.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(beep boop 🤖): Bump uv.lock (main, mcore-main) (2026-04-08) #3210: Updates the same submodule files with a different commit pointer bump.
• chore(beep boop 🤖): Bump uv.lock (main) (2026-03-18) #2873: Modifies the same .main.commit and 3rdparty/Megatron-LM submodule reference files.
• chore(beep boop 🤖): Bump uv.lock (main, mcore-main) (2026-04-16) #3352: Performs a similar Megatron-LM submodule version update across the same files.

Suggested reviewers

• yaoyu-33
• ko3n1g

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title claims to bump uv.lock but the actual changes are only to .main.commit and a git submodule reference, not to uv.lock file.	Update the title to accurately reflect the actual changes: something like 'chore: Update commit references for Megatron-LM submodule' would better represent the modifications made.

✅ 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 dependency version pointer updates with no code logic modifications, new features, or significant refactoring.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-ci-container-2026-04-17-r0.4.0-core_r0.17.0

---

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

[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 @.main.commit:
- Line 1: The .main.commit file references a non-existent upstream commit hash
(d6b1813f2bfb867661b154574d76b3c0d395f426); replace it with a valid commit from
the upstream Megatron-LM repo or remove/refresh the file. To fix, fetch and
verify upstream commits (git fetch upstream; git rev-parse/upstream/main or git
ls-remote upstream) to obtain a reachable commit SHA, then update the value in
.main.commit to that verified SHA (or delete the file if it should not pin a
commit) and re-run your verification to ensure git no longer reports "not our
ref".

🪄 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: Pro Plus

Run ID: e3c68249-414a-44e5-8e58-75cb0e4f8553

📥 Commits

Reviewing files that changed from the base of the PR and between 8684053 and 6de03f1.

⛔ 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 | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify the new commit hash exists in the Megatron-LM submodule

# Check if the commit exists in the submodule
cd 3rdparty/Megatron-LM
git cat-file -t d6b1813f2bfb867661b154574d76b3c0d395f426 2>/dev/null
if [ $? -eq 0 ]; then
  echo "✓ Commit d6b1813f2bfb867661b154574d76b3c0d395f426 exists"
  git log -1 --oneline d6b1813f2bfb867661b154574d76b3c0d395f426
else
  echo "✗ Commit d6b1813f2bfb867661b154574d76b3c0d395f426 not found in submodule"
  echo "Fetching latest changes..."
  git fetch origin
  git cat-file -t d6b1813f2bfb867661b154574d76b3c0d395f426
fi

Repository: NVIDIA-NeMo/Megatron-Bridge

Length of output: 361

---

Do not merge: commit hash does not exist in upstream Megatron-LM repository.

The commit d6b1813f2bfb867661b154574d76b3c0d395f426 referenced in .main.commit cannot be resolved in the upstream Megatron-LM repository. Git returned the error: not our ref. This indicates the commit is not reachable and likely does not exist. Verify the commit hash is correct or obtain a valid commit from the upstream repository before proceeding.

🤖 Prompt for AI Agents

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

In @.main.commit at line 1, The .main.commit file references a non-existent
upstream commit hash (d6b1813f2bfb867661b154574d76b3c0d395f426); replace it with
a valid commit from the upstream Megatron-LM repo or remove/refresh the file. To
fix, fetch and verify upstream commits (git fetch upstream; git
rev-parse/upstream/main or git ls-remote upstream) to obtain a reachable commit
SHA, then update the value in .main.commit to that verified SHA (or delete the
file if it should not pin a commit) and re-run your verification to ensure git
no longer reports "not our ref".