Skip to content

chore(deps): AUT-952 bump Megatron-Core main ref - #5020

Closed
svcnemo-autobot wants to merge 4 commits into
NVIDIA-NeMo:mainfrom
svcnemo-autobot:chore/bump-mcore-main-260722
Closed

chore(deps): AUT-952 bump Megatron-Core main ref#5020
svcnemo-autobot wants to merge 4 commits into
NVIDIA-NeMo:mainfrom
svcnemo-autobot:chore/bump-mcore-main-260722

Conversation

@svcnemo-autobot

@svcnemo-autobot svcnemo-autobot commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Background

Refresh the nightly Megatron-Core main pin from 58bf14e9 to a0462819.

What changed

  • Update .main.commit and the Megatron-LM gitlink.
  • Refresh the full uv.lock dependency set while retaining revision 2.
  • Add the model verification card skill to the docs toctree.

Details

The full lock refresh advances compatible transitive releases. The docs entry fixes pre-existing main drift from #4909: its new skill page was not included in any toctree, causing release docs to fail with warnings treated as errors.

Tested

  • uv lock --upgrade reproduced the committed lock with no diff.
  • Locked sync, pre-commit, installation, wheel build, and wheel validation passed.
  • Exact Sphinx --fail-on-warning gate is running on the docs fix.

…1be45

Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
@svcnemo-autobot

Copy link
Copy Markdown
Collaborator Author

/ok to test e375c01

@yaoyu-33

Copy link
Copy Markdown
Contributor

MCore bump auto-fix status for main:

Classification: no code fix
Evidence: On 2026-07-22 at 07:02 PDT, PR #5020 head e375c016f11dee8bbce9e7d0f8f16a7566cdec8e has no failed check. Installation, lint, DCO, and wheel build/validation passed. The CICD container builds and release docs remain queued or in progress. The MCore range 58bf14e9e68915a5e0c7d70451620e6e713c07d5...a046281960c13d034267cf15cc3b689048a1be45 contains only GitHub workflow hardening and on-call schedule changes, with no Bridge runtime API change.
Fix PR: not opened
Guards: none
Validation: GitHub checks on the current head passed installation (UV - Python3.12 - AMD64/Linux - NGC PyTorch), lint, DCO, and release wheel build/validation; full CICD is non-terminal, so no CW interactive test was required or started.
Next action: let terminal CI finish; rerun the main auto-fix worker only if the current head develops an actionable failure.

@svcnemo-autobot

Copy link
Copy Markdown
Collaborator Author

💬 Agreed with the main auto-fix classification: PR #5020 still has no failed checks, installation/lint/DCO/wheel validation remain green, and authoritative CICD is non-terminal at container builds. No main code fix, guard, or retry is needed; I’m continuing to wait on terminal CI alongside the dev and companion MLM PRs.

Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
@svcnemo-autobot svcnemo-autobot added needs-more-tests Requires additional L0 and L1 test coverage before merge labels Jul 22, 2026
@svcnemo-autobot

Copy link
Copy Markdown
Collaborator Author

/ok to test 19012c6

@yaoyu-33 yaoyu-33 added area:build Dependencies, packaging, images, and environment setup ci CI, automation, test queue, or workflow infrastructure work needs-review PR is ready for code review and waiting on a reviewer labels Jul 22, 2026
@yaoyu-33 yaoyu-33 closed this Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:build Dependencies, packaging, images, and environment setup ci CI, automation, test queue, or workflow infrastructure work full-test-suite needs-more-tests Requires additional L0 and L1 test coverage before merge needs-review PR is ready for code review and waiting on a reviewer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants