chore(beep boop 🤖): Bump uv.lock (main, mcore-dev) (2026-06-25)

[svcnvidia-nemo-ci]

🚀 PR to bump uv.lock in main.

🤖 This PR will be merged automatically once CI passes.

[svcnvidia-nemo-ci]

/ok to test 0b790d5

[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.

[yaoyu-33]

MCore bump auto-fix status for dev:

Classification: MCore broke Bridge
Evidence: 2026-06-25 main/mcore-dev bump PR #4497 updates .dev.commit from cf081d5df0b34b665d214ff936f27489d7396876 to 4463f78179d67691bf6a00f9c2e3062ca9fe41db and 3rdparty/Megatron-LM from a58373f332496f08c6584b3196233275ff69f175 to 4463f78179d67691bf6a00f9c2e3062ca9fe41db. Launch_Unit_Tests_Core run 28164125325, job 83422433967, completed on 2026-06-25 at 04:45 PDT, fails the same three Gemma4 PLE tests: test_patch_ple_block_threading_injects_layer_inputs_and_restores_state, test_patch_ple_block_threading_wraps_checkpointed_forward, and test_threads_per_layer_inputs_to_each_layer. The current job log shows AttributeError: module 'megatron.core.transformer.transformer_block' has no attribute 'checkpointed_forward'; Nemo_CICD_Test job 83423889425 is the aggregate failure. MCore compare a58373f332496f08c6584b3196233275ff69f175...4463f78179d67691bf6a00f9c2e3062ca9fe41db is diverged (523 commits ahead, 50 behind), with tip 4463f78179d6 [dev] Megatron Lite (4/4) shared attention (#5427).
Fix PR: #4445 (existing open fix PR; no duplicate branch or PR opened for #4497)
Guards: no new guards added in this 2026-06-25 07:45 PDT worker session. Existing fix PR #4445 adds a local feature guard in src/megatron/bridge/models/gemma/modeling_gemma4.py for the old module-level checkpointed_forward API; its removal TODO is when both MCore main and dev call TransformerBlock._checkpointed_forward directly. Removed guards: none.
Validation: no new local or CW validation was run because existing open fix PR #4445 already covers this target failure. Existing #4445 validation reports 2026-06-22 America/Los_Angeles CW interactive focused Gemma4 PLE selectors with uv run --no-sync python -m pytest ... -q -> 4 passed, 35 warnings; full Gemma4 unit files with uv run --no-sync python -m pytest tests/unit_tests/models/gemma/test_gemma4_modeling.py tests/unit_tests/models/gemma/test_gemma4_provider.py -q -> 123 passed, 37 warnings; uv run --no-sync pre-commit run --all-files -> passed. GitHub CI on #4445 passed Launch_Unit_Tests_Core on run 28053348546, job 83074814061, completed on 2026-06-23 at 16:02 PDT. Current #4445 blockers appear unrelated to the Gemma4 unit fix: Launch_Import_Check, UV - Python3.12 - AMD64/Linux - NGC PyTorch, and release build/publish checks.
Next action: do not open another dev autofix PR. Review or unblock existing fix PR #4445, then rerun CI on #4497 after #4445 merges or after the equivalent Gemma4 PLE fix is applied.