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

[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 module references and version pointers for dependency management.

[svcnvidia-nemo-ci]

/ok to test bbdb5b1

[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

Updated the stored Megatron-LM commit reference in .main.commit and the corresponding git submodule pointer in 3rdparty/Megatron-LM from commit d7288711ba278d160d2a5a22c099915c9fe1395c to 9539a12e1b04a68423f57b3eb41d6125161dca24.

Changes

Cohort / File(s)	Summary
Megatron-LM Submodule Update .main.commit, 3rdparty/Megatron-LM	Updated both files to reference the same new commit hash for the Megatron-LM external dependency.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(beep boop 🤖): Bump uv.lock (main, mcore-main) (2026-03-29) #3016: Updates both .main.commit and 3rdparty/Megatron-LM submodule pointer to different target commits.
• chore(beep boop 🤖): Bump uv.lock (main, mcore-main) (2026-03-24) #2968: Performs identical code-level changes by updating .main.commit and 3rdparty/Megatron-LM submodule pointer to different target hashes.
• chore(beep boop 🤖): Bump uv.lock (main, mcore-main) (2026-04-08) #3210: Changes the same submodule pointer and .main.commit file, updating Megatron-LM commit references.

Suggested reviewers

• ko3n1g
• yaoyu-33

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title mentions bumping 'uv.lock' but the actual changes only update commit identifiers in '.main.commit' and a Megatron-LM submodule pointer, not the uv.lock file.	Update the title to accurately reflect the actual changes, such as 'chore: Update Megatron-LM submodule and main commit pointer' or similar.

✅ 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 management changes (uv.lock, submodule pointers, commit identifiers) labeled as chore maintenance with minimal code review effort and no impact on core functionality.

_{✏️ 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-16-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 `@3rdparty/Megatron-LM`:
- Line 1: The submodule pointer for 3rdparty/Megatron-LM is referencing a
non-existent commit (9539a12e1b04a68423f57b3eb41d6125161dca24); fix by verifying
and updating the submodule reference: check .gitmodules for the Megatron-LM
remote URL, ensure it matches the upstream NVIDIA/Megatron-LM repo, run git
submodule sync && git submodule update --init --remote 3rdparty/Megatron-LM to
fetch reachable commits, then reset the submodule pointer to a valid commit or
branch (replace the bad hash in the superproject commit) and commit that update
so the pointer references an existing upstream commit.

🪄 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: d48c7c4e-5328-4d71-b896-7eba7eae466b

📥 Commits

Reviewing files that changed from the base of the PR and between f4d10a3 and bbdb5b1.

⛔ 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 Megatron-LM submodule commit exists upstream and examine changes

# Navigate to the submodule directory
cd 3rdparty/Megatron-LM || exit 1

# Fetch latest from upstream to ensure we have the commit
git fetch origin

# Verify the new commit exists
echo "=== Verifying new commit exists ==="
if git cat-file -t 9539a12e1b04a68423f57b3eb41d6125161dca24 2>/dev/null; then
    echo "✓ Commit 9539a12e1b04a68423f57b3eb41d6125161dca24 exists"
else
    echo "✗ Commit 9539a12e1b04a68423f57b3eb41d6125161dca24 NOT FOUND"
    exit 1
fi

# Show commit message for the new commit
echo -e "\n=== New commit details ==="
git log -1 --oneline 9539a12e1b04a68423f57b3eb41d6125161dca24

# Show summary of changes between old and new commits
echo -e "\n=== Changes between commits ==="
git log --oneline d7288711ba278d160d2a5a22c099915c9fe1395c..9539a12e1b04a68423f57b3eb41d6125161dca24

# Show files changed
echo -e "\n=== Files changed ==="
git diff --stat d7288711ba278d160d2a5a22c099915c9fe1395c..9539a12e1b04a68423f57b3eb41d6125161dca24

Repository: NVIDIA-NeMo/Megatron-Bridge

Length of output: 166

---

The submodule pointer commit cannot be verified — this will cause build failures.

The commit 9539a12e1b04a68423f57b3eb41d6125161dca24 could not be found after fetching from the upstream repository. This indicates either:

• The commit hash is incorrect or contains a typo
• The commit doesn't exist in the upstream Megatron-LM repository
• The submodule remote URL is misconfigured

Verify that the new commit hash 9539a12e1b04a68423f57b3eb41d6125161dca24 exists in the upstream NVIDIA/Megatron-LM repository and is reachable from the branch being tracked.

🤖 Prompt for AI Agents

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

In `@3rdparty/Megatron-LM` at line 1, The submodule pointer for
3rdparty/Megatron-LM is referencing a non-existent commit
(9539a12e1b04a68423f57b3eb41d6125161dca24); fix by verifying and updating the
submodule reference: check .gitmodules for the Megatron-LM remote URL, ensure it
matches the upstream NVIDIA/Megatron-LM repo, run git submodule sync && git
submodule update --init --remote 3rdparty/Megatron-LM to fetch reachable
commits, then reset the submodule pointer to a valid commit or branch (replace
the bad hash in the superproject commit) and commit that update so the pointer
references an existing upstream commit.

[ko3n1g]

/ok to test

[copy-pr-bot]

/ok to test

@ko3n1g, there was an error processing your request: E1

See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/

[ko3n1g]

/ok to test

[copy-pr-bot]

/ok to test

@ko3n1g, there was an error processing your request: E1

See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/

[ko3n1g]

/ok to test aa0ace4