Skip to content

chore(beep boop 🤖): Bump uv.lock (main, mcore-main) (2026-04-19) - #3411

Closed
svcnvidia-nemo-ci wants to merge 1 commit into
mainfrom
bump-ci-container-2026-04-19-main-main
Closed

chore(beep boop 🤖): Bump uv.lock (main, mcore-main) (2026-04-19)#3411
svcnvidia-nemo-ci wants to merge 1 commit into
mainfrom
bump-ci-container-2026-04-19-main-main

Conversation

@svcnvidia-nemo-ci

@svcnvidia-nemo-ci svcnvidia-nemo-ci commented Apr 19, 2026

Copy link
Copy Markdown
Contributor

🚀 PR to bump uv.lock in main.

🤖 This PR will be merged automatically once CI passes.

Summary by CodeRabbit

  • Chores
    • Updated internal dependency references to the latest upstream versions.

Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@svcnvidia-nemo-ci

Copy link
Copy Markdown
Contributor Author

/ok to test 04afcf1

@copy-pr-bot

copy-pr-bot Bot commented Apr 19, 2026

Copy link
Copy Markdown

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

coderabbitai Bot commented Apr 19, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e73e3b2c-2f68-4a64-aba9-b9ffd4aab8fe

📥 Commits

Reviewing files that changed from the base of the PR and between 57308b4 and 04afcf1.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • .main.commit
  • 3rdparty/Megatron-LM

📝 Walkthrough

Walkthrough

The pull request updates the Megatron-LM submodule reference to a newer upstream commit. Both the .main.commit tracking file and the 3rdparty/Megatron-LM submodule pointer are advanced to the same commit hash, synchronizing the pinned upstream code version.

Changes

Cohort / File(s) Summary
Megatron-LM Submodule Bump
.main.commit, 3rdparty/Megatron-LM
Updated submodule pointer from commit 23265d2db37efa883b3983bce321c631898822f3 to afae25b5f0c04ae747d9d48e855bb7df2221ce52, advancing the tracked upstream Megatron-LM code version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • yaoyu-33
  • ko3n1g
🚥 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 are to '.main.commit' and '3rdparty/Megatron-LM' submodule references, not the lock file. The title is misleading about what was changed. Update the title to accurately reflect the changes, such as 'chore: Update Megatron-LM submodule reference' or clarify what 'uv.lock' refers to in this context.
✅ 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 lock file updates and submodule reference bumps managed by automated CI, requiring no test documentation.

✏️ 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-19-main-main

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

@yaoyu-33

Copy link
Copy Markdown
Contributor

Superseded by the 2026-04-20 bump.

@yaoyu-33 yaoyu-33 closed this Apr 20, 2026
@yaoyu-33
yaoyu-33 deleted the bump-ci-container-2026-04-19-main-main branch April 20, 2026 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants